跳到正文
cccskills
免费在 GitHub 公开

branch-from-issue

Create a git branch named after a GitHub issue.

中文简介正在准备中。当前显示原文说明。

集成工具GitHub
查看安装方法

包含的文件(1)

  • SKILL.md2.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Create branch from GitHub issue

Step 1: Read the issue title

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.

Step 2: Slugify the title

Convert the issue title to a branch-safe slug:

  1. Convert to lowercase
  2. Replace spaces and punctuation with hyphens
  3. Remove any characters that are not letters, digits, or hyphens
  4. Collapse consecutive hyphens into one
  5. Strip leading and trailing hyphens
  6. Truncate to 40 characters maximum (truncate at a word boundary if possible)

Examples:

  • "Fix login page crash on mobile" → fix-login-page-crash-on-mobile
  • "Add support for OAuth 2.0 / PKCE flow" → add-support-for-oauth-20-pkce-flow
  • "Update README with installation instructions" → update-readme-with-installation

Step 3: Determine the branch prefix

If $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.

Step 4: Create the branch

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.

Step 5: Confirm

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

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.

中文简介正在准备中。当前显示原文说明。

davila7/claude-with-skills132026年5月15日 更新

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.

中文简介正在准备中。当前显示原文说明。

davila7/claude-with-skills132026年5月15日 更新

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.

中文简介正在准备中。当前显示原文说明。

davila7/claude-with-skills132026年5月15日 更新

Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.

中文简介正在准备中。当前显示原文说明。

davila7/claude-with-skills132026年5月15日 更新

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.

中文简介正在准备中。当前显示原文说明。

davila7/claude-with-skills132026年5月15日 更新

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.

中文简介正在准备中。当前显示原文说明。

davila7/claude-with-skills132026年5月15日 更新

查看 davila7 的全部技能

报告此技能的问题