Loading...
Loading...
Found 4,188 Skills
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Execute Tests - walks through test cases from the test plan, collects results, and updates the plan. Use when verifying a feature implementation.
Operator-invoked review of the full branch (every commit vs. the base branch) plus any uncommitted local changes before opening or updating a PR. Strict gatekeeper stance with per-diff and branch-level checks. Language-agnostic.
Use before commit or review when the operator wants to quickly understand the current staged, unstaged, untracked, branch, or PR diff without reading a long audit.
Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
Execute an implementation plan through to a verified, committed code change. Use after `plan-implementation` produces the ordered `Stages` plan.
Push a branch and open it as a pull request, drafting its title and description from context. Use when a task is ready to present for integration.
Get user sign-off on a set of commits, routing any requested changes through fix-feedback until confirmed, then autosquash resulting fixups. Use before a batch of commits is finalized (pushed, submitted as a PR) whenever the caller wants a human confirmation step first.
[user/auto] 진행 중 작업의 검증된 `handoff snapshot`을 작성하거나 기존 `handoff`를 명시적으로 재개합니다. 작업 목표 계약은 `seed.md`, 진행 상태는 `handoff.md`가 소유합니다. 일반 요약이나 평범한 계속하기에는 적용하지 않습니다.
[user] 설정된 repository들의 open pull request를 deterministic fresh triage로 읽고, 지금 처리할 일과 기다릴 일을 자연스럽게 브리핑한 뒤 한 번 승인된 범위에서 bounded multi-PR maintenance를 수행합니다.
[user/auto] 의도 증거를 바탕으로 활성 `merge`, `rebase`, `cherry-pick`, `revert` 충돌을 해결하고 작업을 완료합니다. 활성 충돌이 없는 일반 파일 수정에는 적용하지 않습니다.