- Skills
- 76
- 仓库
- 1
- 职业覆盖
- 4
- 场景覆盖
- 6
- Stars
- ★ 10
Daniel Moretti 的 Skills 76
changelog
Write the changelog entry for a pull request. Use when a PR changes behavior that users, operators, or integrators can notice.
writing-good-tickets
Write, file, or update an issue or ticket that an agent or a developer can take to one PR. Use when filing a bug or feature, updating an issue, or breaking a plan into tickets.
writing-good-prs
Write or update a pull request title and body that a reviewer can trust and own. Use when opening a PR or editing its description.
writing-good-commits
Write or reword a git commit message and size the commit it describes. Use when committing, or when reshaping commits during a rebase.
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Use how for runtime behavior.
web-search
Find and read live web sources when the answer needs evidence unavailable in the current context.
unslop
Cut AI tells from any writing. Use for any prose surface, your reply to the user included.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
triage
Turn a batch of tickets someone else wrote into agent-ready work, with duplicates closed, stale tickets dropped, decisions grilled, and a parent spec over sub-tickets with blocking edges.
to-tickets
Break a plan, spec, or the current conversation into tracer-bullet tickets, each declaring its blocking edges, published to the project's issue tracker. Use when the user asks to split a spec or plan into tickets or issues.
to-spec
Synthesize the current conversation into a spec and publish it to the project's issue tracker, without an interview. Use when the user asks for a spec or PRD of what was discussed, or to file the agreed plan as a spec ticket.
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
Test-first red-green loop for features and bug fixes. Use when building a feature or fixing a bug whose behavior has a cheap local test target, or when the user asks for TDD, a failing test, or a regression test. Skip when the test path is unclear, expensive, or integration-heavy.
swarm
Fan out N parallel workers, drain them, and return one report. Use for 'swarm this', or parallel coverage, races, gauntlets, and exploration.
subagents
Read before using subagents.
statechart
Draw how any system moves between states, such as a product flow, a protocol, or a service, as a Mermaid statechart from a TLA+ model. Each bug is a numbered path with blue borders to a state that breaks a rule. Use to show a bug as a path through states, or to turn an agreed chart into a TLA+ skeleton.