Loading...
Loading...
Found 102 Skills
Work GitHub issues with command arguments: create/draft, update, critique, narrow, widen, merge, clean, refine, explain, document, close, reopen, search, and status. Default with only an issue identifier (and optional details) is execute completion work — plan/diagnose/implement/test/ready-check/merge — not issue-admin. Explicit commands still do admin. Rough idea with no identifier defaults to `create`. Use when the user asks about issues, `/issues <command|#n|url|idea>`, drafting or improving an issue, or finishing tracked work.
Manage GitHub Issues 2.0 relationships with gh CLI: parent issues, sub-issues, blocked-by, and blocking links.
Read and set work state on the CLHbid Delivery board — the delivery language, issues via gh, the Status field, the board query recipes, cycles, epics, labels, the commit convention and the decomposition rules. Use for any GitHub issue or project-board operation in a clhbid repo, and for what a cycle, epic or slipped issue means.
Create lean-spec style GitHub issues as specs for human-AI aligned implementation on the current repo. Use when asked to "create a spec", "write a spec issue", "spec this feature", "spec this", or when planning work that needs a specification before implementation. Follows the lean-spec SDD methodology — small focused specs (<2000 tokens), intent over implementation, context economy. Creates GitHub issues with Overview, Design, Plan, Test, Alignment, and Notes sections. Repo-specific area taxonomy, sister-skill names, custom body sections (e.g. Provider impact / Schema impact / Reach), and additional principles are overlaid by the consumer repo's CLAUDE.md and its `*-dev-process` / `*-pre-push` / `*-pr-lifecycle` sister skills — read those first when the repo isn't obvious.
Own the GitHub issue lifecycle with five modes: create issues from a plan or description (kept independent for parallel worktree work), start a `ready` issue into its own worktree, close one out once its PR merges, sync PR↔issue links after merge, and triage the tracker for lifecycle and priority gaps. Use when the user says "create issues from this plan", "file an issue", "start issue #42", "close #42", "wrap up #42 now the PR merged", "sync my issues", "triage the backlog", "prioritize my issues", "set the priority on #42", "issuekit", or wants issues opened, started, landed, reconciled, ranked, or reviewed with the gh CLI.
Implements a feature or a fix that has been documented in a Github issue
Activates a work item or issue and creates the feature branch in one step. Supports ADO work items and GitHub issues, selected via the ISSUE_TRACKER config setting. Use when the user says "start story", "start working on", "begin AB#N", "kick off AB#N", "start issue
Implement one GitHub Issue at a time — tests, review, gates, commit. Never mirror tickets to disk.
Implementiert alle offenen GitHub Issues eines Repositories vollautomatisch in einem Rutsch. Issues, die voneinander unabhängig sind, werden parallel über Subagents abgearbeitet; abhängige Issues laufen sequenziell. Jede Implementierung wird per `/tdd` test-getrieben entwickelt, über Playwright-MCP verifiziert, bei Fehlern mit `/diagnosing-bugs` analysiert und nach Caveman-Prinzipien (`/caveman`) vereinfacht. Erfolgreiche Implementierungen werden committet, der User bekommt erst nach Abschluss aller Issues eine Sammelmeldung. Nutze diesen Skill IMMER, wenn der User sagt "implementiere alle issues", "alle gh issues", "issues aus github abarbeiten", "batch implementation", "parallel issues bearbeiten", "alle offenen tickets" oder ähnliches — auch ohne explizite Nennung von Playwright/TDD/Caveman, da diese Werkzeuge zum Standard-Workflow gehören.
Break a plan into tracer-bullet tickets with blockers and publish via issue-tracker. Local files only if asked.
Create a plan for the specified task and store it as GitHub issues in the repository of the current working directory. Given the URL of a GitHub issue, it turns that issue into the parent "plan" issue (Goal, Context and a checklist of phases) and creates one child issue per phase, linking every phase as a native GitHub sub-issue of the parent. Stops for user approval before creating any issue. After creation, the plan is meant to be implemented with the codely-plan-phase-implement-github skill.
Interview the requester, then draft and file a complete Elastic documentation issue against the right template and repository — enforcing the good-issues quality bar, checking for duplicates and existing coverage first, rewriting implementation-side detail into user-facing terms, and routing sensitive requests privately. Use it to request docs for a feature, hand off notes or a pull request, request a UI copy review, report a problem with a published page, share support feedback privately, or ask how to request documentation support.