本文へ移動
cccskills
無料GitHub で公開

routine-logic-simplifier

Autonomous maintenance routine that finds one convoluted unit of business logic in a monorepo package — deep nesting, boolean spaghetti, interleaved concerns — pins its behavior with tests, simplifies it in place with zero behavior change, and ships via /ship. Use only when the user explicitly invokes /routine-logic-simplifier or asks to simplify convoluted existing logic. SKIP for reviewing the current diff (/simplify), removing indirection layers (routine-abstraction-improver), and fixing wrong behavior (routine-logic-bugfixer). The core trigger is "make this convoluted logic read simply without changing what it does".

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/beancount-ioスター 315(GitHub 315 + cccskills 0)

実行スコア 未検証

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Task: Simplify convoluted business logic, behavior-preserving

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

Pick one genuinely convoluted unit, pin its current behavior with tests, rewrite it in place so it reads simply, prove nothing changed, 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

Find hotspots worth the risk:

  • git log --oneline -- <pkg> — files that keep appearing in fix: commits; churn is where convolution costs the most.
  • Read for the smells: nesting past ~3 levels, long boolean chains, one function interleaving parsing + decision + formatting, repeated re-derivation of the same intermediate value.

Pick one unit (a function or a small cluster). Convoluted-but-working code nobody touches is a weak finding; convoluted code with churn is a strong one.

3. Prove it (pin first)

  • Existing tests must cover the unit's observable behavior, or you write pinning tests first — inputs/outputs as they are today, including the weird edges.
  • If the behavior cannot be safely pinned (nondeterminism, giant I/O surface), skip the finding — an unpinned simplification is a gamble, not maintenance.

4. Fix

Simplify in place: flatten nesting with early returns, name the intermediate values, split interleaved concerns into local helpers. Introduce no new abstractions — no new interfaces, layers, or files unless splitting one oversized file is itself the simplification. Zero behavior change, byte for byte where observable.

5. Verify

Pinning tests and the owning package's full gate, all green. The pinning tests ship with the change.

6. Ship

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

What NOT to do

  • Never fold a behavior change into the refactor. A bug discovered mid-simplify is a separate routine-logic-bugfixer finding — note it, finish the behavior-preserving simplification, report the bug in the summary.
  • Don't remove indirection layers (single-impl interfaces, passthrough wrappers) — that is routine-abstraction-improver's job.
  • Don't "simplify" by deleting handling for edge cases you can't prove unreachable — that's how convoluted code got its reputation for being load-bearing.
  • Don't reformat or rename beyond the unit you picked; keep the diff reviewable.

Arguments

$ARGUMENTS

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

Prepare supported accrual and reversal drafts for a period from an explicitly stated schedule — basis, service interval, day-count, recognized-to-date, already-booked, required adjustment — posted only through the suite's propose/confirm/check flow with stable schedule identity. Skip recording one-off entries the user describes (beancount-add), explaining how a balance moved (beancount-roll-forward), tax or depreciation advice, automatic reversals, and ledgers hosted on Beancount.io.

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/beancount-io3152026年10月26日 更新

Record one-off entries the user describes in a local Beancount ledger through bea — a purchase, bill, paycheck, or transfer between their own accounts (including splits and pasted receipt text), opening or closing an account, a price, or a note. Propose the exact entries from existing accounts, check whether one is already recorded, and write only after confirmation with a passing check; it never changes existing entries. Skip bank or card export files (beancount-import), statements (beancount-reconcile), finance-app migrations, options trades (beancount-options), investment trades, dividends, splits, and vests (beancount-trade), month-end close, edits to existing entries, and ledgers hosted on Beancount.io.

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/beancount-io3152026年10月26日 更新

Answer explicit requests for facts from a local Beancount ledger using shown, reproducible bea queries and reports for spending, trends, net worth, holdings, subscriptions and anomalies. Do not select this skill merely to gather preliminary inputs for buy/sell decisions or tax recommendations, even if ledger facts could help. Strictly read-only; figures come from executed queries. Skip ledgers hosted on Beancount.io, recording transactions (beancount-add), reconciliation, migration, ledger edits, option pricing or greeks, investment or tax advice, and general Beancount, BQL, or `bea` documentation questions (including what `bea ask` does).

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/beancount-io3152026年10月26日 更新

Close an accounting period in a local Beancount ledger by reconciling each active account through beancount-reconcile, checking assertions and recurring gaps, reviewing flags, then proposing a commit with the period reports. Use for month-end close or wrapping up the books. Surface incomplete work and require a passing check before a confirmed commit; never push. Skip closing a single account (a `close` directive; beancount-add) and ledgers hosted on Beancount.io.

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/beancount-io3152026年10月26日 更新

Record bank/card transactions in an existing local Beancount ledger from CSV, OFX/QFX, QIF or PDF statements, including PDF-only banks with no CSV export. For a PDF ledger import, read this SKILL.md before the PDF helper's guide to establish account, deduplication and confirmation rules, then use the helper for extraction. Import broker activity CSVs or holdings/cost-basis exports as lot-carrying entries or opening lots. Read this guide before beancount-trade for these files; skip described trades (beancount-trade). Normalize signs, suggest categories from existing accounts, review duplicates and confirm before bea writes; PDF statements must tie out and end with a balance assertion. Skip standalone PDF extraction/OCR, summarization or editing without a ledger import; account-versus-statement comparisons (beancount-reconcile), full finance-app migrations, reusable importer authoring, individual options trades, single manual entries (beancount-add), ledger `option` settings, and ledgers hosted on Beancount.io.

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/beancount-io3152026年10月26日 更新

Write or repair a reusable Beangulp importer from a sample bank export for a local ledger, with reviewed golden files and a passing test harness. Use when a source needs a tested Python importer or its format changed, e.g. "write a beangulp importer for my bank's CSV" or "my importer broke after the bank renamed its columns". Wire the confirmed runner through bea ingest; keep generate/test in the authoring project. Skip one-off imports, reconciliation, finance-app migration, ledger writes, and ledgers hosted on Beancount.io.

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/beancount-io3152026年10月26日 更新

bex-co のスキルをすべて見る

このスキルの問題を報告する