branch-commit

Solid

Return a branch name and a concise commit message (at most 2 lines) for the current task, grounded in the real `git diff` rather than a paraphrase of the task summary, and with `--apply` optionally create that commit after showing it and getting the user's confirmation in the same turn. Use when the user only needs quick branch and commit naming right before committing, full PR packaging is unnecessary, and there is a real inspectable diff (staged or unstaged changes, or a branch diff vs an integration base); use `--apply` when the commit-evidence closure floor needs a commit to exist. Do not use when the task needs a complete PR package (use pr-package), there is no diff yet (naming a branch from a task summary alone is the failure mode this command exists to avoid; ask the user to stage at least one change first), or the diff is still too unclear to summarize safely.

Code & Development 6 stars 0 forks Updated 5 days ago MIT

Install

View on GitHub

Quality Score: 81/100

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

Skill Content

Act as a concise engineering delivery assistant. Goal: Return a branch name and a concise commit message for the current task, grounded in the real `git diff` rather than a paraphrase of the task summary. Mandatory context bootstrap (before any output): <!-- shared:mandatory-context-bootstrap --> - Read these sections in `WORKFLOW_OPERATING_SYSTEM.md` first: - `## LLM execution contract` - `## Editor mode policy` (mode definitions only; the tool mapping table is lazy-loaded in `wos/editor-mode-mappings.md` and needed only for non-Claude-Code tools) - `## Global output contract` (including **Adaptive handoff** and **Mode selection rule**) - `## Cross-cutting workflow guardrails` - **Bootstrap tiers (ADR-0025):** the light-weight commands (`branch-commit`, `what-next`, `where-we-at`, `slice-closure`, `compact-task-memory`) may skip `## Editor mode policy` good-fits lists and `## Cross-cutting workflow guardrails` sequencing heuristics, reading only the mode definitions and the core guardrail rules (routing memory, command-less input triage, official command names, material change, no-op). The full tier is measured at 9610 tokens: the combined size of the four always-read `WORKFLOW_OPERATING_SYSTEM.md` sections listed above. The reduced tier is a self-declared estimate of about 3,500 tokens for the trimmed subset above; it has not been independently re-measured by the same method, and should be read as an estimate rather than a fresh figure. The same reduced tier exten...

Details

Author
Mozurok
Repository
Mozurok/fhorja.dev
Created
1 months ago
Last Updated
5 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

commit

Git commit workflow with conventional commits, branch creation, push, and PR support. Use when the user asks to commit, save changes, push, ship it, open a PR, send a PR, or says "/commit". Also triggers on short aliases: "cp" (commit and push), "cb" (commit to new branch), "cpr" (commit and PR). Trigger phrases: "commit", "commit and push", "commit new branch", "commit to new branch", "commit and pr", "commit push pr", "commit pr", "cp", "cb", "cpr", "push this up", "save my changes", "ship it".

0 Updated 2 days ago
svyatov
Code & Development Listed

branch-recap

Takes stock of what a branch actually changed, before it gets pushed — works out the scope itself, then lays the change out group by group in one pass: files touched, what was done and why, how, and what deserves a second look, quoting code only where a remark needs it rather than reprinting the diffs. Closes on a single question set so the user steers without wading through hunks, and can then file the fixes decided along the way into the commits they belong to, via fixup and autosquash. Use it whenever someone wants to find out what happened on their own unmerged work — "relis ma branche", "on repasse sur mes commits", "vérifier ce que j'ai fait hier soir", "qu'est-ce que j'ai changé au juste sur cette branche", "fais le point avant que je pousse", "repasser sur ce que j'ai fait avant de demander une revue", "check my work before I open the MR/PR", "walk me through my changes" — including when the code was produced fast with an assistant and they no longer know what is in there, when they only name a commit

2 Updated 6 days ago
Malo-T
Code & Development Solid

commit

Group changes into one atomic commit, draft a Conventional Commit message in COMMIT_AGENTMSG, put it through an independent review and the commit-msg gates, confirm it with the operator, then commit and rebase. Use this skill whenever the user asks to commit work in a tbhb repo ("commit this," "commit the staged changes," "write a commit message") or whenever a task ends in creating a commit.

73 Updated 2 days ago
tbhb