verify-invoices
Drive the real invoices CLI against sample data and record evidence. Use after changing CLI behavior.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- verify-invoices
- description
- Drive the real invoices CLI against sample data and record evidence. Use after changing CLI behavior.
02 资源文件 2
- 脚本drive.py802 B
- 参考文档recipes.json134 B
03 SKILL.md 正文
Verify invoices
Run python3 .agents/skills/verify-invoices/drive.py from the project root. It runs each recipe in recipes.json through the real CLI, compares the output, and writes .verify/last-run.json.
Recipes
- summary-default:
summary fixtures/sample.csvprints the invoice count and total.
Add or update a recipe in recipes.json when user-facing CLI output changes. Keep one recipe per user path.
04 同仓库更多 Skills
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
unslop
Cut AI tells from any writing. Must always apply.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.