Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
The full commit workflow for BIND 9 repositories — pre-commit clang-format sequence, message shape and 72-column wrapping, trailer rules (Assisted-by and the forbidden ones), amend/fixup discipline…
$ npx skills add isc-projects/bind9 --skill bind-commit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install isc-projects/bind9 bind-commit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/isc-projects/bind9.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bind-commit .claude/skills/bind-commit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "bind-commit" agent skill from https://github.com/isc-projects/bind9/tree/main/.agents/skills/bind-commit into .claude/skills/bind-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bind-commit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/isc-projects/bind9/tree/main/.agents/skills/bind-commitType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add isc-projects/bind9 --skill bind-commit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install isc-projects/bind9 bind-commit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/isc-projects/bind9.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/bind-commit .agents/skills/bind-commit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bind-commit" agent skill from https://github.com/isc-projects/bind9/tree/main/.agents/skills/bind-commit into .agents/skills/bind-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bind-commit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add isc-projects/bind9 --skill bind-commit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install isc-projects/bind9 bind-commit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/isc-projects/bind9.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/bind-commit .cursor/skills/bind-commit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "bind-commit" agent skill from https://github.com/isc-projects/bind9/tree/main/.agents/skills/bind-commit into .cursor/skills/bind-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bind-commit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/isc-projects/bind9.git --path .agents/skills/bind-commit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add isc-projects/bind9 --skill bind-commit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install isc-projects/bind9 bind-commit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/isc-projects/bind9.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/bind-commit .gemini/skills/bind-commit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "bind-commit" agent skill from https://github.com/isc-projects/bind9/tree/main/.agents/skills/bind-commit into .gemini/skills/bind-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bind-commit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install isc-projects/bind9 bind-commitInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add isc-projects/bind9 --skill bind-commit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/isc-projects/bind9.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/bind-commit .github/skills/bind-commit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "bind-commit" agent skill from https://github.com/isc-projects/bind9/tree/main/.agents/skills/bind-commit into .github/skills/bind-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bind-commit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add isc-projects/bind9 --skill bind-commit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install isc-projects/bind9 bind-commit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/isc-projects/bind9.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/bind-commit .opencode/skills/bind-commit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "bind-commit" agent skill from https://github.com/isc-projects/bind9/tree/main/.agents/skills/bind-commit into .opencode/skills/bind-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bind-commit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
bind-commitThe full commit workflow for BIND 9 repositories — pre-commit clang-format sequence, message shape and 72-column wrapping, trailer rules (Assisted-by and the forbidden ones), amend/fixup discipline…
Bind Commit is an agent skill from isc-projects/bind9. The full commit workflow for BIND 9 repositories — pre-commit clang-format sequence, message shape and 72-column wrapping, trailer rules (Assisted-by and the forbidden ones), amend/fixup discipline, and the never-push boundary. Use EVERY time you are about to create, amend, reword, or fix up a commit in any BIND 9 checkout.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Git. The repository describes itself as: Archived mirror of https://gitlab.isc.org/isc-projects/bind9, please submit issues and PR/MRs in the GitLab. The licence is MPL-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 12d28b2. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitghglabFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, gh and glab, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Bind Commit loads about 1.1k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 561 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from isc-projects/bind9 at commit 12d28b2, republished under its MPL-2.0 licence (© isc-projects). 561 words, ~1,064 tokens.
.claude/skills/bind-commit/SKILL.md (or your agent's skills folder).git add <files>git-clang-format HEAD — the hyphenated binary. git clang-format
(with a space) invokes a nonexistent git subcommand and fails. It
operates on STAGED files only.git add any reformatted files, then commit.Only format C lines you wrote or edited yourself. If the working-tree diff was authored by the user (their editor, their patch), do NOT run clang-format over it — it is not your code to reformat.
new:/fix:/dev:/doc: prefix — those appear
only on GitLab-generated MR-merge commits. Real branch-commit style:
git log --no-merges --first-parent.git commit -m does NOT wrap: a
long paragraph becomes one unwrapped line that sticks out
immediately. Write the message pre-wrapped to a file and use
git commit -F <file>, or pass each physical line as its own -m.Assisted-by: <tool>:<model-id> format, which specialized analysis
tools to list after the model id (never trivial tooling), no
Signed-off-by: from the agent, no Co-Authored-By: or any AI
co-author line.Assisted-by ONLY when the LLM wrote the load-bearing
code/test/config content of the commit. NOT for: rewording a
message, squashing fixups, review-only advice, or a comment/doc
block added around a user-authored fix — a comment is prose, not the
fix; do not rationalize "the comment was AI" to keep the trailer.Claude-Session:
and anything else the harness would like to stamp on the message
(session/conversation ids, transcript links, "generated with"
footers). A commit message is for the reviewer and the log, not for
agent telemetry; dangerfile.py rejects Claude-Session: outright.
If such a trailer shows up in a message you are about to commit,
strip it before committing.Closes #N / Fixes #N / Refs #N — issue refs go in the MR
description; the branch name already encodes the issue number.HEAD, polish-only (typo, message tightening, whitespace): plain
--amend; keep the original author (git's default).
HEAD, implementation replaced by a different approach:
--amend --reset-author (or explicit --author=) — attribution
follows whoever wrote the NEW code, not whoever wrote the discarded
version. When in doubt about amending someone else's commit, ask
first. The Assisted-by question is independent — re-derive it from
who authored the new content.
NOT HEAD: NEVER rebuild the branch with git reset --hard <older> +
cherry-pick (this once collided with the user's concurrent rebase and
trashed the branch). Instead add a fixup commit on top:
git commit --fixup=amend:<hash>git commit --fixup=reword:<hash> — it opens an
editor and ignores -m; supply the wrapped message via
GIT_EDITOR='cp /path/to/msg.txt'git commit --fixup=<hash>Then STOP and hand git rebase -i --autosquash <base> to the user —
never run the rebase yourself.
Before ANY history operation run git status; if a rebase or
cherry-pick is in progress, do not touch the branch.
Commit locally only. Never git push (any variant), never
gh pr create / glab mr create. When the work is finished, hand the
MR title/description over as text (see the bind-mr-description skill)
— do not offer to push or open the MR.
© isc-projects, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/bind-commit of isc-projects/bind9.
Open the folder on GitHubat commit 12d28b2
Bind Commit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Bind Commit this skillisc-projects/bind9 | 780 | — | ~1.1k | Automated safety check: Pass | MPL-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
isc-projects/bind9
BIND 9's memory allocator wrapper (iscmem memory contexts and iscmempool fixed-size pools).
isc-projects/bind9
Correct discipline for mutating an RCU / lock-free pointer-based data structure (trie, tree, list, graph) that has concurrent readers — build a new node cluster invisibly, publish it, then reclaim…
isc-projects/bind9
Measure and fix C struct layout in BIND 9 — pahole on the build's DWARF for sizes, padding holes, and cacheline boundaries, plus the house cacheline-padding idiom.
isc-projects/bind9
Review and refine ISC BIND 9 release notes for a new version — audit audience/action tags against the actual change substance, verify every covered issue is closed, and rewrite the auto-generated…
isc-projects/bind9
Drafting BIND 9 merge-request titles and descriptions — they feed the generated release notes, so the audience is system administrators.
isc-projects/bind9
How BIND 9 schedules callbacks — iscjobrun (same loop), iscasyncrun (any thread → any loop), iscworkenqueue (offload to a worker thread).
Works with
Categories
The full commit workflow for BIND 9 repositories — pre-commit clang-format sequence, message shape and 72-column wrapping, trailer rules (Assisted-by and the forbidden ones), amend/fixup discipline…. Bind Commit is an agent skill from isc-projects/bind9. The full commit workflow for BIND 9 repositories — pre-commit clang-format sequence, message shape and 72-column wrapping, trailer rules (Assisted-by and the forbidden ones), amend/fixup discipline, and the never-push boundary.
Bind Commit fits situations like: development work in your project.
Run `npx skills add isc-projects/bind9 --skill bind-commit -a claude-code`. Or copy the skill folder (.agents/skills/bind-commit in isc-projects/bind9) into .claude/skills/bind-commit in your project. Claude Code loads it when a task matches its description.
Run `npx skills add isc-projects/bind9 --skill bind-commit -a codex`. Or copy the skill folder (.agents/skills/bind-commit in isc-projects/bind9) into .agents/skills/bind-commit in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add isc-projects/bind9 --skill bind-commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bind-commit, .gemini/skills/bind-commit, .github/skills/bind-commit and .opencode/skills/bind-commit in your project.
Going by SKILL.md and its folder, Bind Commit needs the command-line tools its instructions call (git, gh and glab).
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Bind Commit is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Bind Commit: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
isc-projects (a GitHub organization) maintains it in isc-projects/bind9, which has 780 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.
Source: isc-projects/bind9 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.