Loading...
Loading...
Found 5,605 Skills
Complete GitHub pull requests by iterating on CI and review feedback until the PR is ready.
Run Codex, Claude Code, and Gemini CLI reviews against the current branch concurrently, deduplicate the findings, and fix only the review comments that are still valid for the current codebase.
Run Claude Code review against the current branch, fix only the review comments that are still valid for the current codebase, and leave invalid comments unchanged.
Run Codex code review against the current branch, fix only the review comments that are still valid for the current codebase, and leave invalid comments unchanged.
Check the latest test-related CI results for the current pull request.
하네스 시스템 안내 전문가. "어떤 스킬", "어떻게", "도움말", "help", "가이드", "어디서 시작" 키워드로 트리거. 스킬 추천, 워크플로우 안내, 시스템 개념 설명을 제공하는 읽기전용 온보딩 스킬. (skills.sh 글로벌 설치 안내 포함)
Break an approved spec into ordered implementation tasks with dependencies, sequencing logic, and done criteria.
Update repo documentation and agent-facing guidance such as AGENTS.md, README.md, docs/, specs, plans, and runbooks. Use when code, skill, or infrastructure changes risk doc drift or when documentation needs cleanup or restructuring. Do not use for code review, runtime verification, or `agent-readiness` setup.
Use when batch-resolving approved todos, especially after code review or triage sessions
Conduct a targeted code exploration of the repository, and document the process of "Ask Questions → Read Code → Draw Conclusions" as searchable evidence for direct reuse when similar questions arise next time. There are three types: question (investigate code around a specific question and provide conclusions), module-overview (sort out the structure, boundaries, entry points, and dependencies of a module), and spike (conduct lightweight technical exploration of multiple possible directions without making final decisions). Trigger scenarios: Users say "Let's explore first", "How is X implemented in this repository", "Quickly get familiar with this module", "Archive the exploration results". Refer to `codestable/reference/system-overview.md` for how to distinguish it from learning / tricks / decisions.
Onboard a new repository or a repository with scattered documents into the CodeStable system. Two paths are automatically determined: the empty repository path (no spec-type documents or codestable/ directory in the repository) builds the skeleton from scratch; the migration path (the repository already has scattered documents or partial codestable/ structure) first generates an audit report + migration mapping plan, which is finalized after user confirmation one by one. This skill only does two things: "build the skeleton" and "organize existing documents". Once the skeleton is built, all sub-workflows can run directly. Trigger scenarios: Users say "Use CodeStable in this project", "Build CodeStable structure", "Initialize CodeStable", "Migrate to CodeStable".
Enter this sub-process when conducting code optimization — handle tasks where 'behavior remains unchanged, structure changes' (structure / performance / readability). Shift single-module internal optimization from 'AI random refactoring' to 'first scan to generate a checklist, confirm each item with the user, execute step-by-step according to the method library, and require manual approval for each step'. Trigger scenarios: Users mention phrases like 'optimize it / refactor / rewrite / split it / poor performance / code is too long' without any accompanying behavior changes. Do not handle new requirements (route to feature), bugs (route to issue), or cross-module architecture restructuring (route to architecture + decisions).