Create a git branch named after a GitHub issue.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Run:
gh issue view $issue
Extract the issue title from the output. If the issue does not exist or gh is not authenticated, stop and report the error.
Convert the issue title to a branch-safe slug:
Examples:
fix-login-page-crash-on-mobileadd-support-for-oauth-20-pkce-flowupdate-readme-with-installationIf $prefix is not empty, use it as provided.
If $prefix is empty, use feature as the default prefix.
Valid examples: feature, fix, chore, hotfix. Accept any non-empty string the user provides.
Construct the full branch name: $prefix/$issue-<slug>
For example, if $prefix is fix, $issue is 142, and the slug is login-page-crash-on-mobile:
fix/142-login-page-crash-on-mobile
Run:
git checkout -b $prefix/$issue-<slug>
If the branch already exists, report the conflict and stop. Do not force-create or checkout the existing branch automatically.
Report the new branch name and confirm the current branch has switched:
git branch --show-current
Example output:
Created and switched to: fix/142-login-page-crash-on-mobile
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
The English summary is being prepared. Showing the original description.
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
The English summary is being prepared. Showing the original description.
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
The English summary is being prepared. Showing the original description.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Run a comprehensive code quality audit covering security, performance, and maintainability. Use for quarterly audits, pre-release reviews, or when onboarding to a large codebase.
The English summary is being prepared. Showing the original description.