3.3천건 · 관련도순
Govern the SemVer release process — versioning discipline, tag-based GitHub releases, changelog hygiene, and the ADR that confirms the release strategy is agreed. Trigger when setting up a release process, before a first public release, or when release practice has become inconsistent. Owned by delivery-orchestrator.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the complete release workflow: changelog entry, version bump, git tag, and GitHub release. Invokes changelog-entry, tag-version, and publish in sequence. Use when releasing a new version of the project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Push the current branch and all tags to origin, then create a GitHub release using the latest tag and its CHANGELOG.md entry. Use after tag-version to complete a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a git branch named after a GitHub issue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run all code quality checks (security, complexity, test coverage) on the current PR and post a combined report as a GitHub PR comment. Use before merging a PR, during code review, or when asked to check code quality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix a GitHub issue by number. Reads the issue, implements a fix, and prepares a commit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Squash the current branch's work into a single commit and open (or update) a GitHub pull request with Graphite (`gt`). Use when asked to "create a PR", "open a pull request", "put this up for review", or to update an existing PR for the current branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Product Owner - scans codebase and creates or amends GitHub issues with PRD. Use when: PRD, feature, issue, create issue, amend issue, what should we build, plan feature, design feature, scope, requirements, user story.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implementer - fetches a GitHub issue, builds an implementation plan, then implements using TDD. Use when: implement, build this, code this, add this feature, TDD, test first, red green refactor, pick a task, next task, dev.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
TDD pair programming with mode switching. Claude can be driver (writes code) or navigator (watches, questions, provokes). Supports GitHub issues, file watching, or arbitrary prompts. Scientific TDD, baby steps, one test at a time. Trigger on: pair, let's pair, tdd, you drive, I'll drive, dojo.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tune the GitHub Copilot AI — `copilot-instructions.md`, PR-review patterns, suggestion behavior, output verbosity. NOT for dev-environment setup (use `devcontainer`).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Wire up DevContainers / GitHub Codespaces — `devcontainer.json`, container images, secrets, VS Code features, port forwarding. NOT for tuning Copilot itself (use `copilot-config`).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user invokes a slash command like /create-pr, /commit, /fix-ci, or pastes command file content — routes to the right command with context inference and GitHub API patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity. Use when invoked as `$work-track-item` or when the user asks to track a work item.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Post findings from the most recent review output as inline GitHub PR comments and record them in today's daily note. Use when invoked as `$pr-post-review-findings` or when the user asks to post review findings to the current PR.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured, risk-aware code review of a GitHub pull request using the gh CLI, with diff triage, unresolved-thread suppression, and severity-grouped findings ending in an approve/request-changes verdict.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or update a GitHub pull request for the current branch. Use when the user invokes `$pr-create`, asks to create/open a PR, or wants the current branch pushed and described as a draft PR.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stack an existing or new git branch on top of another branch, restacking it in a git worktree when needed, then align the GitHub PR bases and stack metadata with `gh stack`. Use when invoked as `$git-stack` or when the user asks to stack or restack a branch or PR onto another branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Approve a GitHub pull request, inferring the target from context when no PR is given. Use when the user invokes `$pr-approve`, asks to approve a PR, or approves a pull request mentioned earlier in the conversation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Address GitHub PR review comments at line, file, and PR level by fetching, evaluating, fixing, committing, and resolving feedback. Use when invoked as `$pr-resolve-review-feedback` or when the user asks to resolve PR feedback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Dashboard d'avancement des epics en cours. Thin wrapper sur les scripts bash qui agrègent les logs per-agent (.claude/state/epic_run/) et le state GitHub. Pas de LLM lourd. Usage: /report [<epic_N> ...]
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.