- Skills
- 13
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 0
Jacob 的 Skills 13
tdd
Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
task-observer
Use when the user asks to log a skill observation, review the observation log, run a skill review, or discuss skill taxonomy, or says "One Skill to Rule Them All". Not for a subagent dispatched by a session already running it: that subagent puts its findings in its report.
software-factory
Use when designing a software factory, choosing the services it plugs into, or defining the tasks it runs.
no-comments
Use when the user wants scoped code comments reviewed, accepted findings fixed, or claimed constraints encoded as enforceable checks.
no-ai-slop
Use when the user wants a draft edited to read clearer, more direct, more opinionated, or less AI-sounding, wants AI-slop patterns flagged without a rewrite, or asks whether writing reads as AI.
merged
Use when a pull request has merged and the local repo should be cleaned up for the next piece of work, whether the user says so, runs /merged, or wait_merged.sh exits 0.
leaving-pr-comments
Use when posting any comment, review reply, or dismissal reason on GitHub on the user's behalf.
improve
Use when the user wants an audit, improvement opportunities, roadmap advice, or an implementation handoff from a read-only senior-advisor survey of a codebase.
implement-spec
Use when the user wants the result of /to-spec and /to-tickets implemented in code.
grilling
Use when the user wants a plan, decision, or idea stress-tested before acting on it, or uses any 'grill' trigger phrase.
diagnosing-bugs
Use when the user says "diagnose"/"debug this", or reports a hard bug, a flaky or intermittent failure, or a performance regression (something broken, throwing, failing, or slow), including when handing its fix to a subagent.
council
Use when the user asks to consult the council, wants several models to sign off on a PR, branch, or plan before it merges or ships, or says to merge "once they're happy".
code-review
Use when a branch is ready for its PR, or the user asks to review a branch, a PR, work-in-progress changes, or the changes "since X".