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

routine-shipped-feature-inliner

Autonomous maintenance routine that finds gates for fully shipped features — flags, env switches, boolean guards that have held one value everywhere for a long time — triages deliberate gates from forgotten ones, inlines the enabled path, deletes the dead branch and the flag itself, and ships each removal via /ship. Use only when the user explicitly invokes /routine-shipped-feature-inliner or asks to clean up shipped/stale feature flags. SKIP for unreachable code not behind a flag (routine-dead-code-removal) and for changing what any flag is set to — this routine never flips a value. The core trigger is "this feature fully shipped; remove its flag and inline the winning path".

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

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

実行スコア 未検証

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.7 KB

SKILL.md(原文)

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

Task: Remove gates for fully shipped features

Usage: /routine-shipped-feature-inliner [package-or-path]

Find a flag whose decision has already been made everywhere, prove it is forgotten rather than deliberate, inline the path it always takes, delete the other branch and the flag definition, 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

Grep the package for gate shapes:

  • mobile/src/config.ts → config.features.* compile-time constants
  • process.env.* used as a boolean switch; values seeded in .env.example and deploy configs (deploy/, root bex.yaml)
  • is*Enabled / enable* booleans, route guards, early returns on a config value

3. Prove it — deliberate gate vs forgotten flag (mandatory triage)

A flag is only a finding when all of these hold:

  1. It holds one value in every environment: grep every setter and reader, .env.example, deploy configs — no environment or code path flips it.
  2. Nothing marks it deliberate: check root .pm/DO_NOT_DO.md, the package's .pm/DO_NOT_DO.md, docs/adrs/, and code comments at the definition.
  3. git log on its introduction and last value change shows it has sat at its final value for a while, with no sign of a pending decision.

Any evidence of intent → not a finding; note it as skipped.

4. Fix

Inline the path the flag always takes. Delete: the now-dead branch, the flag definition, its plumbing (props/params that only carried it), and tests that only exercised the removed branch. Update tests that asserted the flag's value to assert the now-unconditional behavior. Never change the flag's value on the way out — inline only flags already at their final value.

5. Verify

Owning package's full gate per the contract. If the flag guarded UI, verify the surviving path still renders (mobile: light and dark per mobile/AGENTS.md).

6. Ship

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

What NOT to do

  • NEVER inline, remove, or flip config.features.agentChat. The mobile agent-chat surface stays gated off by owner decision (mobile/.pm/DO_NOT_DO.md) — it is a deliberate gate, permanently out of scope.
  • The backend featureFlags GraphQL field is a cross-package contract (backend-cluster/backend-v2/src/features/ledger/api/resolvers/ledger-legacy-resolver.query.ts, consumed by the mobile app). Removing or reshaping it is a coordinated multi-package change — report it, don't fix it (universal STOP).
  • Never delete unflagged dead code — that is routine-dead-code-removal's job.
  • Never "finish shipping" a feature by turning its flag on. Flipping a value is a product decision, not maintenance.

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

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