Loading...
Loading...
Found 236 Skills
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues and PRs.
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.
Implement a set of GitHub issues in parallel - triage or take an explicit issue list, group by file-conflict, create a worktree per lane, delegate to sub-agents, open a PR per lane; never merges. Use when asked to implement issues, work the backlog, or pick up multiple issues in parallel.
Run one autonomous GitHub issue-triage tick and route issues through the canonical states.
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.
Fix a bug reported in a GitHub issue or a markdown file, without letting the report's noise and guesses into the main context. Takes an issue number, an issue URL, or a file path as an argument. Use when asked to fix, investigate, or reproduce a reported bug.
Show open GitHub Issues assigned to you in the target repo, grouped by priority label (P0 first), with clickable issue links. Use whenever the user asks "what's on my plate", "my GitHub issues", "what should I work on next", "show my open issues", or starts the day wanting their remaining work. Read-only — it lists, it never changes anything.
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.
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.
Fetch a GitHub issue body and its messages as YAML for the current repository.
Implements a feature or a fix that has been documented in a Github issue
File contributor or agent papercuts as GitHub issues labeled friction, or investigate those issues as the daily friction-log Cloud Agent. Use when you hit repo friction, when asked to log friction, or when spawned to resolve open friction issues.