メニュー
Create a feature branch from a GitHub issue and set up the working context. Use whenever starting implementation on a new issue — creates the branch, fetches requirements, and begins building automatically.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | start-work |
| description | Create a feature branch from a GitHub issue and set up the working context. Use whenever starting implementation on a new issue — creates the branch, fetches requirements, and begins building automatically. |
| allowed-tools | Bash, Read, mcp__github-mcp-server__get_issue |
| user-invocable | true |
Create a feature branch from a GitHub issue and prepare the working context.
{issue} — GitHub issue number (required). Pass as argument: /start-work 42git status for uncommitted changes. Warn the user if the tree is dirty.{username}/{issue-number}-{short-slug}
Derive {username} from the git config user.name (lowercase, no spaces). Derive {short-slug} from the issue title (lowercase, hyphens, max 50 chars, no special characters).
Examples:
makigjuro/42-device-group-assignmentsmakigjuro/15-bundle-versioning-apiFetch the issue using MCP for structured data:
mcp__github-mcp-server__get_issue(owner: "signalbeam-io", repo: "signalbeam-edge", issue_number: {issue})
This returns structured JSON with title, body, labels, and state — no CLI parsing needed.
# Check working tree
git status --short
# Update main and create branch
git fetch origin main
git checkout -b {branch-name} origin/main
Once the branch is created, do not stop. Immediately continue with implementation:
/add-entity, /add-command, /add-query, /add-event-handler, /add-migration, /add-feature) where they apply. Commit logically after each meaningful change./complete-task to go through the full completion workflow (build, lint, tests, review, PR).Do not ask the user what to do next. Read the issue, plan the work, and start building. Only ask clarifying questions if the issue has genuine ambiguity that blocks implementation.
After branch creation, report:
## Ready to Work
- Branch: `{branch-name}`
- Issue: #{issue} — {title}
- Labels: {labels}
### Acceptance Criteria
{parsed AC from issue}
### Implementation Plan
{task list derived from issue analysis}
Starting implementation...
gh issue view {number}.Verify hexagonal architecture layer rules, Result pattern usage, and coding conventions. Use as a quick local check during development — fast and focused on architecture rules only. For full security + quality review, use /code-review instead.
Review code changes for security, architecture, and quality issues. Use for deep PR-level review — checks OWASP vulnerabilities, hexagonal architecture violations, code smells, and test gaps. For a quick architecture-only check, use /check-architecture instead.
Complete current task with all quality gates, code review, QA check, and submit PR. Use when implementation is done and you want to run the full verification pipeline (build, lint, tests, review, QA) and create the pull request.
Complete infrastructure task — lint, validate, review, and submit PR. Use when an infrastructure-only branch is ready for submission — runs Terraform/Helm validation and creates the PR, skipping .NET/frontend checks.
Scaffold a new frontend feature module with page, components, API service, and hooks. Use whenever the user wants to add a new page, dashboard section, UI module, or frontend feature to the React app.
Capture a screenshot of a URL or route with one command. Use whenever the user wants to take a screenshot, capture a page, see what a route looks like, or visually verify a page. Supports mobile viewport with --mobile and unauthenticated mode with --no-auth.