- Skills
- 13
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 0
William Dennis 的 Skills 13
writing-great-skills
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
session-retro
Use at the end of meaningful work to capture lessons, follow-ups, and process improvements.
grilling
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
grill-me
A relentless interview to sharpen a plan or design.
dev-workflow
Use when making a non-trivial code, test, configuration, or documentation change that should be planned, implemented, and verified end-to-end.
code-review
Use when reviewing a change, pull request, diff, or patch for bugs, regressions, missing tests, and maintainability risks.
caveman
Use when the user asks for caveman mode, terse mode, fewer tokens, less detail, or very brief technical communication.
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Explicit invocation only: load solely when the user names it ("brooks-test" / "brooks test"). Never infer from generic test-quality or failing-test requests. Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Explicit invocation only: load solely when the user names it ("brooks-sweep" / "brooks sweep"). Never infer from generic "fix everything" or cleanup requests. Do NOT trigger for: read-only audits or health reports where the user only wants findings without code changes; single-dimension reviews (use the focused skill instead: brooks-review / brooks-audit / brooks-debt / brooks-test); server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime.
brooks-review
PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Explicit invocation only: load solely when the user names it ("brooks-review" / "brooks review"). Never infer from generic review, feedback, or "does this look right?" requests. Do NOT trigger for: questions about how to write code from scratch, language syntax questions, or framework/tool questions where no existing code is shared.
brooks-health
Combined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Explicit invocation only: load solely when the user names it ("brooks-health" / "brooks health"). Never infer from generic quality, health-score, or "run all the checks" requests. Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).
brooks-debt
Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Explicit invocation only: load solely when the user names it ("brooks-debt" / "brooks debt"). Never infer from generic tech-debt, refactoring, or cleanup requests. Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.
brooks-audit
Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Explicit invocation only: load solely when the user names it ("brooks-audit" / "brooks audit"). Never infer from generic architecture, structure, or onboarding requests. Do NOT trigger for: PR-level code review (use brooks-review) or line-level refactoring questions — this skill analyzes structural/module-level concerns, not individual functions.