New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Routine Logic Bugfixer

by bex-co in bex-co/beancount-io

Autonomous maintenance routine that picks one tricky logic unit in a monorepo package — state machines, date/period math, sign conventions, dedup windows, pagination — models its states and edge…

MITAuto-check passedTesting & QA

Install Routine Logic Bugfixer

skills CLI
$ npx skills add bex-co/beancount-io --skill routine-logic-bugfixer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bex-co/beancount-io routine-logic-bugfixer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bex-co/beancount-io.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/routine-logic-bugfixer .claude/skills/routine-logic-bugfixer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
routine-logic-bugfixer
GitHub stars
295
Token cost
~860 tokens
SKILL.md length
383 words
Files
1
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

Autonomous maintenance routine that picks one tricky logic unit in a monorepo package — state machines, date/period math, sign conventions, dedup windows, pagination — models its states and edge…

  • Works in 6 steps: Scope → Discover → Prove it → …
  • Explicitly invokes /routine-logic-bugfixer
  • SKILL.md covers Contract, Workflow, What NOT to do and Arguments
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Routine Logic Bugfixer is an agent skill from bex-co/beancount-io. Autonomous maintenance routine that picks one tricky logic unit in a monorepo package — state machines, date/period math, sign conventions, dedup windows, pagination — models its states and edge cases exhaustively, proves any divergence from documented intent with a failing test, lands the minimal root-cause fix plus regression test, and ships via /ship. Use only when the user explicitly invokes /routine-logic-bugfixer or asks to hunt for logic bugs. SKIP for test-infrastructure failures and intermittent tests…

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Failing and flaky tests, Root cause analysis and Monorepo tooling. The repository describes itself as: 💰 Double-entry bookkeeping made easy — plain-text accounting for humans and AI agents. Polished iOS & Android app built with React Native + Expo. The licence is MIT.

When your agent uses it

  • Explicitly invokes /routine-logic-bugfixer
  • Asks to hunt for logic bugs
  • Is model this tricky logic and fix whats provably wrong

Example prompts

  • “model this tricky logic and fix what”
  • “/routine-logic-bugfixer”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Scope
  2. Discover
  3. Prove it
  4. Fix
  5. Verify
  6. Ship

What it can do on your machine

Read from SKILL.md and the folder at commit 2103ca1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Routine Logic Bugfixer loads about 860 tokens when it runs. Until then it costs about 178 tokens; SKILL.md has 383 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~178
When it runs · the whole SKILL.md, loaded when a task matches
~860

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bex-co/beancount-io at commit 2103ca1, republished under its MIT licence (© bex-co). 383 words, ~860 tokens.

Download SKILL.mdSave it as .claude/skills/routine-logic-bugfixer/SKILL.md (or your agent's skills folder).
name
routine-logic-bugfixer
description
Autonomous maintenance routine that picks one tricky logic unit in a monorepo package — state machines, date/period math, sign conventions, dedup windows, pagination — models its states and edge cases exhaustively, proves any divergence from documented intent with a failing test, lands the minimal root-cause fix plus regression test, and ships via /ship. Use only when the user explicitly invokes /routine-logic-bugfixer or asks to hunt for logic bugs. SKIP for test-infrastructure failures and intermittent tests (routine-flaky-test-fixer) and for merely convoluted-but-correct code (routine-logic-simplifier). The core trigger is "model this tricky logic and fix what's provably wrong".

Task: Model tricky logic to find and fix provable bugs

Usage: /routine-logic-bugfixer [package-or-path]

Pick one unit of genuinely tricky logic, enumerate its states and edges, derive inputs that should break it, prove each bug with a failing test against documented intent, fix the root cause, and ship via /ship.

Contract

Read .agents/skills/routine-shared/contract.md first — preconditions, scope resolution, verify gates, ship protocol, budget, universal STOPs. Floor even without it: never ship red; one finding per ship; anything in a DO_NOT_DO.md is a hard STOP.

Workflow

1. Scope

Resolve scope per the contract.

2. Discover

Pick one tricky unit — the kinds this repo actually has: auth/session state machines, date and period arithmetic, amount sign conventions, dedup/fuzzy-match windows, pagination cursors, cache invalidation, balance computation. Then model it explicitly: list every state, transition, and edge (empty input, boundary dates, negative amounts, timezone/DST edges, off-by-one windows, concurrent transitions). From the model, derive candidate-breaking inputs.

3. Prove it

A bug exists only when you have both:

  1. A failing test against current code for a derived input, and
  2. Documented intent the behavior diverges from — code comments, docs, AGENTS.md guidance, beancount semantics, ADRs, or the git history of the unit.

Reproducible crashes found while modeling count as provable bugs (crashing is never the documented intent). If the intent is genuinely ambiguous — the test pins a choice nobody has made — STOP for that finding and report the ambiguity instead of shipping an opinion.

Show full SKILL.md (148 more words)Show less
4. Fix

The minimal root-cause fix, plus the failing test as a permanent regression test. No drive-by refactoring; if the unit also deserves simplification, defer to routine-logic-simplifier in the summary.

5. Verify

New regression test green, full owning-package gate green, and a quick sweep of callers for anyone depending on the old wrong behavior (if someone does, that is an intent ambiguity — STOP and report).

6. Ship

Compose /ship for this one bug. Loop within budget.

What NOT to do

  • Never ship a "fix" whose only justification is that the new behavior seems more reasonable — no documented intent, no bug.
  • Never weaken or delete an existing test to make a fix pass; a conflicting test means conflicting intent — STOP and report.
  • Intermittent failures are not logic bugs — defer to routine-flaky-test-fixer.
  • Don't model units that are trivial or already exhaustively tested; spend the budget where trickiness lives.

Arguments

$ARGUMENTS

© bex-co, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/routine-logic-bugfixer of bex-co/beancount-io.

Open the folder on GitHubat commit 2103ca1

Compare with similar skills

Routine Logic Bugfixer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Routine Logic Bugfixer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Routine Logic Bugfixer this skillbex-co/beancount-io295—~860Automated safety check: PassMIT
Pester Failure AnalysisPowerShell/PowerShell56k—~5.1kAutomated safety check: PassMIT
Diagnoseavibebuilder/claude-prime1201 repos~1.2kAutomated safety check: PassMIT
Test Guidelinesgetsentry/sentry-dart873—~3.1kAutomated safety check: PassMIT
Diagnose a Red Rundifferent-ai/openwork24k—~779Automated safety check: PassCustom licence
Eval Triage And Improvementmicrosoft/eval-guide138—~5.9kAutomated safety check: PassMIT

Similar skills

  • Pester Failure Analysis

    PowerShell/PowerShell

    Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.

    56k GitHub stars~5.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Diagnose

    avibebuilder/claude-prime

    Investigate unexpected behavior and mysterious bugs. An agent skill from avibebuilder/claude-prime.

    120 GitHub starsUsed in 1 repo~1.2k tokens
    Testing & QAAuto-check passed

  • Test Guidelines

    getsentry/sentry-dart

    Official

    Enforce Sentry Dart/Flutter SDK test conventions for naming, structure, and fixtures.

    873 GitHub stars~3.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Diagnose a Red Run

    different-ai/openwork

    Classifies a failing test, typecheck or CI job before any code changes, by recording the failure and running a clean control to show whether it was already broken.

    24k GitHub stars~779 tokensUpdated today
    Testing & QAAuto-check passed

  • Eval Triage And Improvement

    microsoft/eval-guide

    Official

    A skill your agent uses when the user's Copilot Studio agent evaluations have come back and they need to interpret scores, diagnose root causes of underperforming test cases, find remediation steps…

    138 GitHub stars~5.9k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed

  • cmux Package Test Bisect

    manaflow-ai/cmux

    Finds which commit broke a failing Swift package suite in the cmux repo by bisecting on CI, then judges per test whether it went stale or the code regressed.

    28k GitHub stars~1.5k tokensUpdated today
    Testing & QAAuto-check passed

More from bex-co/beancount-io

All 27 skills in this repo

  • Beancount Close

    bex-co/beancount-io

    Close an accounting period in a Beancount ledger by reconciling each active account through beancount-reconcile, checking assertions and recurring gaps, reviewing flags, then proposing a commit with…

    295 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

  • Beancount Import

    bex-co/beancount-io

    Import a bank or card CSV, OFX/QFX, or QIF export into an existing Beancount ledger.

    295 GitHub stars~3k tokensUpdated yesterday
    Auto-check passed

  • Beancount Importer Author

    bex-co/beancount-io

    Write or repair a reusable Beangulp importer from a sample bank export, with reviewed golden files and a passing test harness.

    295 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Beancount Init

    bex-co/beancount-io

    Scaffold a new Beancount ledger with bea init and validation, with optional Fava browser setup when requested.

    295 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check: notes

  • Beancount Options

    bex-co/beancount-io

    Record a described options trade or lifecycle event as validated Beancount transactions through bea, after review and confirmation.

    295 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed

  • Beancount Reconcile

    bex-co/beancount-io

    Reconcile one Beancount account against a CSV statement or pasted PDF text.

    295 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Routine Logic Bugfixer

What does Routine Logic Bugfixer do?

Autonomous maintenance routine that picks one tricky logic unit in a monorepo package — state machines, date/period math, sign conventions, dedup windows, pagination — models its states and edge…. Routine Logic Bugfixer is an agent skill from bex-co/beancount-io. Autonomous maintenance routine that picks one tricky logic unit in a monorepo package — state machines, date/period math, sign conventions, dedup windows, pagination — models its states and edge cases exhaustively, proves any divergence from documented intent with a failing test, lands the minimal root-cause fix plus regression test, and ships via /ship.

When should I use Routine Logic Bugfixer?

Routine Logic Bugfixer fits situations like: explicitly invokes /routine-logic-bugfixer; asks to hunt for logic bugs; is model this tricky logic and fix whats provably wrong.

How do I install Routine Logic Bugfixer in Claude Code?

Run `npx skills add bex-co/beancount-io --skill routine-logic-bugfixer -a claude-code`. Or copy the skill folder (.agents/skills/routine-logic-bugfixer in bex-co/beancount-io) into .claude/skills/routine-logic-bugfixer in your project. Claude Code loads it when a task matches its description.

How do I install Routine Logic Bugfixer in Codex?

Run `npx skills add bex-co/beancount-io --skill routine-logic-bugfixer -a codex`. Or copy the skill folder (.agents/skills/routine-logic-bugfixer in bex-co/beancount-io) into .agents/skills/routine-logic-bugfixer in your project. Codex loads it when a task matches its description.

Can I use Routine Logic Bugfixer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bex-co/beancount-io --skill routine-logic-bugfixer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/routine-logic-bugfixer, .gemini/skills/routine-logic-bugfixer, .github/skills/routine-logic-bugfixer and .opencode/skills/routine-logic-bugfixer in your project.

What does Routine Logic Bugfixer need to run?

SKILL.md names no scripts, command-line tools or credentials: Routine Logic Bugfixer is instructions for the agent only.

Does Routine Logic Bugfixer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Routine Logic Bugfixer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Routine Logic Bugfixer use?

Routine Logic Bugfixer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Routine Logic Bugfixer use?

About 860 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Routine Logic Bugfixer?

Skills that share tags, products or a category with Routine Logic Bugfixer: Pester Failure Analysis (PowerShell/PowerShell, 56k stars), Diagnose (avibebuilder/claude-prime, 120 stars), Test Guidelines (getsentry/sentry-dart, 873 stars) and Diagnose a Red Run (different-ai/openwork, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Routine Logic Bugfixer?

bex-co (a GitHub organization) maintains it in bex-co/beancount-io, which has 295 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 7, 2026.

Source: bex-co/beancount-io on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.