跳到正文
cccskills
免费在 GitHub 公开

speckit-git-feature

Validate Jira/JPD ticket reference and create a feature branch

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

opsmill/infrahub
集成工具Jira
查看安装方法

包含的文件（1）

  • SKILL.md2.5 KB

SKILL.md（原文）

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

Speckit Git Feature Skill

Create Infrahub Feature Branch

Create and switch to a new git feature branch for the given specification, enforcing an Infrahub Jira or JPD ticket reference as the branch name suffix.

User Input

$ARGUMENTS

Prerequisites

  • Verify Git is available by running git rev-parse --is-inside-work-tree 2>/dev/null
  • If Git is not available, warn the user and skip branch creation

Step 1: Resolve Ticket Reference

Parse $ARGUMENTS for a ticket ID matching either of these formats:

  • JPD format: infp-[0-9]+ (e.g., infp-460)
  • Jira epic format: ifc-[0-9]+ (e.g., ifc-2140)

If no ticket ID is found in the arguments, prompt the user:

"Please provide a Jira or JPD reference for this feature (e.g., infp-460 for a JPD item or ifc-2140 for a Jira epic):"

Do not proceed until a valid ticket ID is provided. Never invent or skip it.

Step 2: Generate Short Name

Generate a concise short name (2-4 words) from the feature description:

  • Use action-noun format when possible (e.g., user-auth, fix-payment-timeout)
  • Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
  • Examples:
    • "Add user authentication" → user-auth
    • "Implement OAuth2 integration for the API" → oauth2-api-integration
    • "Fix payment processing timeout bug" → fix-payment-timeout

Step 3: Create Branch

Construct the branch name as <short-name>-<ticket-id> (e.g., user-auth-infp-460), then pass it as GIT_BRANCH_NAME to bypass the script's automatic numbering:

GIT_BRANCH_NAME="<short-name>-<ticket-id>" .specify/extensions/git/scripts/bash/create-new-feature.sh --json "<feature description>"

Example:

GIT_BRANCH_NAME="user-auth-infp-460" .specify/extensions/git/scripts/bash/create-new-feature.sh --json "Add user authentication"

IMPORTANT:

  • Always construct GIT_BRANCH_NAME as <short-name>-<ticket-id> — ticket ID is the suffix
  • Always include --json so output can be parsed reliably
  • Run this script exactly once per feature
  • For single quotes in args, use escape syntax: 'I'\''m Groot'

Output

The script outputs JSON with:

  • BRANCH_NAME: The branch name (e.g., user-auth-infp-460)
  • FEATURE_NUM: The ticket ID

评价

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

评论

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

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

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

0 / 1000 字

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

同一仓库的技能

analyzing-ci-flakiness

免费

Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal ledger so flakiness can be tracked over time. TRIGGER when: the user wants to find flaky tests, correlate recent CI failures, check which tests fail across PRs or recover on retry, or refresh the flakiness trend report. DO NOT TRIGGER when: babysitting a single PR's CI until green → monitoring-pull-requests; diagnosing or fixing one specific failing test → the bug-analysis skills.

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

opsmill/infrahub5382026年10月17日 更新

audit-docs

免费

Audits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers, reports gaps, and optionally applies the fixes. TRIGGER when: the user wants to audit or check documentation coverage, find doc gaps after a feature branch, or verify docs are still current for a subject or specific files. DO NOT TRIGGER when: authoring new documentation from scratch → use the add-docs flow; only linting/formatting Markdown → run `uv run invoke docs.lint`.

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

opsmill/infrahub5382026年10月17日 更新

commit

免费

Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr.

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

opsmill/infrahub5382026年10月17日 更新

creating-changelog-entries

免费

Use when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or opening a PR, or whenever asked to add a changelog entry, towncrier fragment, or news fragment.

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

opsmill/infrahub5382026年10月17日 更新

creating-issues

免费

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.

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

opsmill/infrahub5382026年10月17日 更新

creating-prd

免费

Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.

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

opsmill/infrahub5382026年10月17日 更新

查看 opsmill 的全部技能

报告此技能的问题