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

routine-useless-test-pruner

Autonomous maintenance routine that finds tests that cannot fail — no real assertions, tautologies that assert a mock returns what it was told, mock-everything tests that never touch the unit — proves it mechanically by breaking the covered behavior and watching the test stay green, deletes them, and ships via /ship. Use only when the user explicitly invokes /routine-useless-test-pruner or asks to prune useless/worthless tests. SKIP for tests that fail intermittently (routine-flaky-test-fixer), tests of code being deleted (they travel with their code), and slow-but-valid tests. The core trigger is "delete tests that can't fail".

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

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

実行スコア 未検証

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.1 KB

SKILL.md(原文)

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

Task: Delete tests that cannot fail

Usage: /routine-useless-test-pruner [package-or-path]

Find tests that pass no matter what the code does, prove it by sabotaging the covered behavior and watching them stay green, delete them, 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. Test roots: mobile/src/__tests__/ (run by the jest-lite runner), dashboard and backend __tests__/ beside features, cli's pytest suite.

2. Discover

Read test files for the shapes that can't fail:

  • No meaningful assertion (only "doesn't throw" on code that can't throw).
  • Tautologies — asserting a mock returns the value the test just told it to return.
  • Mock-everything tests where the unit under test is itself mocked away.
  • Exact or near-exact duplicates of a neighboring test.

3. Prove it — mechanically, every time

For each candidate: temporarily break the behavior the test claims to cover (invert the condition, corrupt the return value), run the test, and observe it still green. Then revert the sabotage immediately. A test that went red is a real test — leave it and move on. Reading alone is never proof.

4. Fix

Default: delete the test. Replace it with a real assertion only when the intended behavior is unambiguous from the test's own name/context and the replacement is a few lines — otherwise deletion is the honest change.

5. Verify

  • git diff must show only test changes — every sabotage fully reverted. This check is part of the finding, not cleanup; a shipped sabotage is the worst outcome this routine has.
  • Owning package's full gate green.

6. Ship

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

What NOT to do

  • Never delete a test that went red under sabotage, however ugly it looks.
  • Never prune a test for being slow, intermittent (routine-flaky-test-fixer), or attached to code some other routine is deleting.
  • Never leave sabotage in the tree — verify the revert with git diff before staging, every time.
  • Don't batch prunings across files into one ship; each finding stays reviewable on its own.

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

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