// Verifying implementation work before claiming completion; covers tests, affected artifacts, evidence, and unresolved risks.
Use when the user explicitly invokes $work or asks for execution strategy for complex engineering work with unclear scope, dependent steps, or separable workstreams.
Preparing and creating git commits when explicitly requested; covers staged diff review, secrets checks, and conventional commit messages.
Create a conventional commit from current workspace changes. Use when the user asks to run $commit, asks to commit changes, or asks for a commit message from the current diff.
Create GitHub issues with optional parent/sub-issue relationships and organization issue types. Use when the user asks to create, link, or retag GitHub issues, especially when they mention a parent issue, sub-issues, tasks, bugs, epics, or cross-repo issue hierarchy.
Extract the underlying intent behind a request, issue, PR, or diff. Focus on problem and desired outcome; do not propose implementation, testing strategy, or rollout plans.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
| name | verification |
| description | Verifying implementation work before claiming completion; covers tests, affected artifacts, evidence, and unresolved risks. |
| condition | Use before saying work is done, complete, fixed, ready, verified, or when the user asks if something is done. |
Use this skill before claiming non-trivial work is complete.
