一键在 Manus 中运行任何 Skill

speckit-git-feature

星标5

分支4

更新时间2026年5月14日 19:22

Create a new git feature branch following the pickup-points-modal naming convention (feat/<slug>, fix/<slug>, chore/<slug>) from latest origin/main.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

vtex

vtex/pickup-points-modal

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

speckit-git-feature

Creates a feature branch following the repo's naming convention.

When to use

At the start of any non-trivial work.
Before speckit-implement.

Naming convention

Prefix	When to use
`feat/<slug>`	User-visible new feature
`fix/<slug>`	Bug fix
`chore/<slug>`	Tooling, docs, deps without functional change
`refactor/<slug>`	Refactor without functional change
`chk-<ticket>`	Checkout team Jira ticket (`chk-NNNN` format)

<slug> is kebab-case, descriptive, max 5 words.

Flow

git fetch origin
git checkout -b feat/<slug> origin/main

Validations

Current branch before creating: ideally main or origin/main.
Working tree clean: anything pending? Stash or commit first.
Branch with the same slug exists? Surface it and ask.

Don't

Don't create a branch off another feature branch that has not been merged yet.
Don't use master (the repo uses main).
Don't force-push to a branch that already has an open PR.

同仓库更多 Skills

同仓库

implementing

vtex/pickup-points-modal

Implement an approved spec end-to-end in the pickup-points-modal repo — branch, code, tests, lint, typecheck, build, commit, and open a PR following Conventional Commits and the project constitution.

2026-05-145

specification

vtex/pickup-points-modal

Generate an SDD (Spec Driven Development) document for a new feature in the pickup-points-modal, covering Business Context, Architectural Decisions, and Technical Contract before any code is written.

2026-05-145

speckit-analyze

vtex/pickup-points-modal

Audit consistency between spec.md, plan.md, tasks.md, and the actual code in the pickup-points-modal — flagging drift, missing tasks, or out-of-spec changes before PR review.

2026-05-145

speckit-checklist

vtex/pickup-points-modal

Generate a per-feature validation checklist (pre-merge gates, manual QA steps, rollback plan) for a pickup-points-modal feature, tailored to the spec and constitution principles.

2026-05-145

speckit-clarify

vtex/pickup-points-modal

Interactively clarify ambiguous requirements in a spec.md before planning — generates targeted questions for the requester to resolve TBDs in the pickup-points-modal feature spec.

2026-05-145

speckit-constitution

vtex/pickup-points-modal

Create or amend the project constitution in .specify/memory/constitution.md, capturing binding principles, governance, and ratification metadata for the pickup-points-modal.

2026-05-145

name	speckit-git-feature
description	Create a new git feature branch following the pickup-points-modal naming convention (feat/<slug>, fix/<slug>, chore/<slug>) from latest origin/main.
type	skill

speckit-git-feature

Creates a feature branch following the repo's naming convention.

When to use

At the start of any non-trivial work.
Before speckit-implement.

Naming convention

Prefix	When to use
`feat/<slug>`	User-visible new feature
`fix/<slug>`	Bug fix
`chore/<slug>`	Tooling, docs, deps without functional change
`refactor/<slug>`	Refactor without functional change
`chk-<ticket>`	Checkout team Jira ticket (`chk-NNNN` format)

<slug> is kebab-case, descriptive, max 5 words.

Flow

git fetch origin
git checkout -b feat/<slug> origin/main

Validations

Current branch before creating: ideally main or origin/main.
Working tree clean: anything pending? Stash or commit first.
Branch with the same slug exists? Surface it and ask.

Don't

Don't create a branch off another feature branch that has not been merged yet.
Don't use master (the repo uses main).
Don't force-push to a branch that already has an open PR.