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

routine-abstraction-improver

Autonomous maintenance routine that flattens over-engineered abstractions in a monorepo package — interfaces with one implementation and no stated reason, passthrough wrappers, one-product factories, delegate-only manager layers — by inlining the single thing behind them and shipping via /ship. Use only when the user explicitly invokes /routine-abstraction-improver or asks to flatten needless indirection. SKIP for convoluted logic inside one unit (routine-logic-simplifier), imports crossing stated boundaries (routine-abstraction-police), and duplicated implementations (routine-dup-unifier). The core trigger is "remove indirection that has exactly one thing behind it".

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

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

実行スコア 未検証

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.2 KB

SKILL.md(原文)

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

Task: Flatten over-engineered abstractions

Usage: /routine-abstraction-improver [package-or-path]

Find a layer of indirection with exactly one thing behind it and no stated reason to exist, inline it, delete the layer, 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

The shapes worth suspecting:

  • Interfaces/abstract classes with exactly one implementation
  • Wrapper functions/modules that only re-export or forward arguments
  • Factories that can only ever produce one product
  • Generics never instantiated with a second type
  • "Manager"/"provider"/"service" layers that purely delegate

3. Prove it

A layer is a finding only when all hold:

  1. Grep confirms exactly one implementation and one usage pattern.
  2. No stated reason for it exists. Check the scoped AGENTS.md, docs/adrs/, and .pm boards. In particular: backend-v2 mandates an I<Name> interface beside every service/workflow class (backend-cluster/backend-v2/AGENTS.md, Dependency and layer rules) — those interfaces are a stated convention, never a finding. Same for seams that exist so tests can double them, when the tests actually do.
  3. No evidence of a planned second implementation.

4. Fix

Inline the single thing, delete the layer, call directly. If tests mocked the deleted layer, rewrite them against the concrete unit with real assertions — never leave them asserting a mock of something that no longer exists. Behavior identical.

5. Verify

Typecheck + full owning-package gate, and a grep confirming no dangling references to the deleted layer.

6. Ship

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

What NOT to do

  • Never flatten an abstraction a AGENTS.md, ADR, or working test double justifies — a stated convention beats this routine's taste, every time.
  • Don't rewrite convoluted logic inside a unit (routine-logic-simplifier) or move code across layers (routine-abstraction-police).
  • Don't flatten two layers in one ship; each deletion stands alone.
  • Don't replace the deleted abstraction with a cleverer one — the fix is less structure, not different structure.

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 のスキルをすべて見る

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