commit

Solid

spec-flow SHIP step: conventional-commit + push + surface the merge/pull-request link, VCS-agnostic (GitHub + GitLab), with a base-branch guard. Branch creation is owned by the lifecycle commands (/sf:ingest, /sf:bug, /sf:change) via the engine's branch-ensure; this skill commits on the current work branch and refuses to commit on the configured base branch. Invoke ONLY in spec-flow context — explicitly as /sf:commit, or from the /sf:phase ship step. Do NOT auto-trigger on a bare "commit"/"commit push" request — that is the user's own commit workflow, not this skill.

Code & Development 0 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
0
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# commit — conventional commit + push (spec-flow) Turn the staged diff into a clean conventional commit, push, and surface the MR/PR link. This skill is **convention only** — no personal style, no stack assumptions. Branch policy lives in `.spec-flow/config.json → branching` and is created by the lifecycle commands, not here. **Multi-repo:** this skill operates on the **current working directory's** git repo only. When `config.repos` is set (one SD across sibling service repos), the caller runs this skill **once per repo with staged changes** — `cd` into each repo first. `branch-ensure` has already created the same `feat/<feature>` branch in each, so each invocation commits + pushes + surfaces one PR for that service; collect the PR links together. ## Modes | Invocation | Behavior | |------------|----------| | `commit` | Commit staged changes on the current branch | | `commit push` | Commit + push + surface MR/PR link | ## Process ### Step 1 — Gather context (run in parallel) ```bash git status --short git diff --cached --stat git diff --stat git log --oneline -5 git rev-parse --abbrev-ref HEAD ``` Collect: current branch, staged files (`git diff --cached --name-only`), unstaged/untracked (informational), and the repo's recent commit style. ### Step 2 — Base-branch guard (spec-flow) If `.spec-flow/config.json` exists, read its `branching` block (`mode`, `base`). - If `branching.mode` is **not** `off` **and** the current branch **equals** `branching.base` (e.g. `m...

Details

Author
tranquocthong
Repository
tranquocthong/claude-spec-flow
Created
1 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category