rsp-commit
Skill1 starsChanged 8 days agoMITView on GitHub
Inspect or create one authorized exact-scope local commit for direct, Change, integration, Group or release delivery. Preserve unrelated work; do not infer lifecycle, remote delivery or history-rewrite authority.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- author-rsp-skillsSkill
- distill-upstreamSkill
- release-acceptanceSkill
- rsp-docSkill
- rsp-implementSkill
- rsp-reviewSkill
- rsp-shapeSkill
- rspSkill
- rsp-verifySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 43
Read nearest authority and the selected current owner, plus the relevant Brief/children or archive when needed.
- Distinctive: line 65
Use native Git inside this capability.
- Very specific: line 74
Read HEAD with git --no-replace-objects rev-parse --verify 'HEAD^{commit}'.
- Very specific: line 84
Read resulting HEAD, then inspect that immutable SHA using git --no-replace-objects cat-file commit <sha> for the raw message, tree and …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
RSP Commit
For tracked work, read the shared work model when its identity and ownership definitions are missing from the current context. Use logical WorkRefs in commands and reports; cite file locations separately. Direct invocation needs no prior Core execution.
Own exact local Git delivery, invoked directly or through Core. This default core capability grants no authority through availability. Readiness-only work stays read-only. Commit only with current local authority, one exact owned boundary and applicable passing verification.
Responses follow explicit instruction, personal instructions, then conversation language; existing artifacts retain theirs. Commit prose follows explicit commit-language instruction, effective configuration, nearest repository authority, then clear recent non-merge style. Response language does not select it. Preserve commands, identifiers, Conventional types/scopes and trailers.
Resolve needed RSP defaults/inheritance through the selected CLI's successful rsp config --json, refreshing on drift or recovery. Raw YAML is diagnostic only. Projection failure leaves dependent language unresolved before staging; history cannot replace it, while independent authorized inspection may continue. Resolve material conflicts with the owner.
Establish the delivery boundary
Resolve the smallest request: kind, purpose, owner or summary, real included WorkRefs when relevant, exact paths, current local authority, applicable verification pointers and lifecycle evidence only when applicable. Derive these facts from direct user intent or Core's bounded handoff; do not require a transport schema or create a second source of truth.
| Kind | Identity and applicable evidence | RSP trailers |
| direct | One confirmed direct outcome permitted by project tracking rules | none |
| change | One real WorkRef | RSP-WorkRef |
| integration | At least two real WorkRefs and one evidenced shared delivery boundary | included RSP-WorkRef values |
| group | Group reference, included WorkRefs and one wave or closeout boundary | RSP-Group and included RSP-WorkRef values |
| release | Confirmed release identity and release-boundary evidence | only real included WorkRefs |
A durable owner is a Change WorkRef or Group reference; included children never replace it. Direct, integration and release may have no durable WorkOwner. Integration creates no Group, direct creates no Change, and commit count is independent from Change count.
Purpose is separate from kind:
- A checkpoint keeps the Change open and delivers a verified current slice without claiming completed acceptance, closing an issue or requiring archive.
- A terminal delivery claims completion only for its selected boundary. Tracked terminal inputs require complete Tasks, decisive Required Verify and no active blocker; legacy unclassified Verify is Required. Optional omissions remain explicit but do not block. Direct work uses its own acceptance, not an invented lifecycle gate.
Before staging a tracked commit, inspect the selected owner's Tasks and actual remaining scope. Incomplete Tasks select a checkpoint; all Tasks complete selects Core closeout, even when Required checks or review are incomplete or failed. Generic commit wording must not bypass that decision. Reuse an explicit applicable checkpoint or closure choice; do not ask twice. For multiple included WorkRefs, assess their boundaries separately rather than infer Group completion. Commit pauses for its owning capability to correct stale records, perform necessary writing or authorized lifecycle work. If terminal delivery includes authorized archive or Group closeout, require that action and its inspected diff before staging. Do not archive, update Specs or clean up a Change inside Commit. A checkpoint still needs its own applicable verification; absent lifecycle authority neither grants closure nor prohibits an otherwise authorized checkpoint.
Audit before staging
Read nearest authority and the selected current owner, plus the relevant Brief/children or archive when needed. Inspect status, the complete staged, unstaged and untracked boundary, cached diff and recent non-merge messages. Reread decisive verification and applicable lifecycle facts; copied handoff prose is insufficient.
Reuse traceable passing results while relevant content, dependencies, configuration, tools, inputs and environment still apply. Run only authorized missing or invalidated checks with settled scope and method, or explicitly required executions; entering Commit alone requires no rerun. Failed or unavailable required evidence stops delivery.
Stop without changing the index on missing or ambiguous authority, stale evidence, an invalid kind/purpose, unrelated staged work, mixed ownership that cannot be separated without guessing, or active merge, cherry-pick, revert, rebase, mail-apply or sequencer state. Preserve pre-existing owned partial staging unless the exact additional content is authorized. Never broaden paths, unstage unrelated work or reset the index to make a boundary fit.
Before reporting eligibility, confirm verification covers the exact proposed content. Matching filenames or a working-tree pass containing excluded changes is insufficient. For a staged slice, compare evidence with the current index. Check excluded code, configuration, fixtures and generated inputs for invalidation. Obtain missing evidence within authority or report the gap; preserve unrelated work.
Before dependent git add or git commit, run required audits and preparation as separately observed commands by default. If batching, explicitly gate each dependent write on all its prerequisites succeeding; shell newlines and the batch's final exit code do not provide that gate. A failed or unavailable prerequisite blocks its dependent write. Inspect actual index/worktree effects before permitted recovery; later success does not erase an earlier write after failure. Commit's one-attempt rule still applies.
For readiness-only work, report eligibility, gaps and the next owner here; do not stage, prepare files or commit.
Review the final index and message
- Stage only the authorized content with exact path handling. Reread status, complete cached paths and diff, including sensitive material, and prove one reviewable logical boundary. Stop if it does not match; do not repair unrelated staging.
- Confirm the final index matches the content covered by the audited evidence. If staging changed that boundary, reassess applicability and fill only missing or invalidated coverage before proceeding; unchanged applicable results need no rerun. Record the reviewed HEAD (or unborn state) and index tree. These bind content, file modes and deletions, not only names; keep them transient.
- Derive the message from that final cached diff, not conversation chronology or a copied Change. Follow applicable project message rules and checks, using the established Conventional form when present and a concise repository-consistent subject. When the project permits and the subject is sufficient, omit the body; otherwise add only the rationale, behavior differences, compatibility or risk needed by a reader without the session.
- Load message and references for tracked, integration, Group, release, issue-related or non-trivial messages. Keep real removals, migration constraints and important omissions; omit session-only attempts, file inventories and routine command output. A supplied prepared message must still match the reviewed boundary; do not edit it when nearer authority forbids editing.
- Prepare actual multiline text, preferably outside the worktree or at an explicitly allowed path. Never use literal backslash-n as a newline transport or include a temporary message file in delivery. Legitimate escape notation in prose stays literal; do not decode it or reject it merely for containing backslash-n.
Execute once and observe
Use native Git inside this capability; no RSP commit wrapper or generated delivery script is required. Missing Commit capability has no Core substitute. Respect a nearer required method or denial; an incompatible requirement needs an owner decision, not a trial commit or automatic fallback.
- Inspect operation state through
git rev-parse --git-pathfor MERGE_HEAD, CHERRY_PICK_HEAD, REVERT_HEAD, rebase-merge, rebase-apply and sequencer. Any active operation or incomplete inspection stops ordinary delivery. Resolve paths through Git, not a presumed .git directory, so worktrees are covered. - Read HEAD with
git --no-replace-objects rev-parse --verify 'HEAD^{commit}'. A failed read is not automatically unborn: requiregit symbolic-ref -q HEADto name refs/heads/... andgit show-ref --verify --quiet <that-ref>to confirm absence (exit 1). Other errors stop. Immediately before execution, recheck this HEAD/unborn state andgit write-treeagainst the reviewed snapshot. A caller's fixed snapshot cannot be replaced on its behalf. Drift stops without index repair. - Attempt exactly once:
git commit --cleanup=verbatim -F <message-file>, replacing the placeholder with the safely prepared, quoted path. Preserve normal hooks and signing policy; do not disable either to obtain success. Snapshot checks are sequential observations, not a cross-process lock. - Read resulting HEAD, then inspect that immutable SHA using
git --no-replace-objects cat-file commit <sha>for the raw message, tree and parents, andgit --no-replace-objects diff-tree --root --no-commit-id --name-only --no-renames -r -z <sha>for actual paths. Use NUL-delimited path observations before and after delivery; do not split unusual filenames on whitespace or treat display quoting as identity. - Require the committed tree and paths to match the reviewed index, one parent equal to reviewed HEAD (no parents for unborn), and the complete stored message to match the prepared text with at most one terminal LF difference. Recheck final HEAD still identifies that SHA and inspect remaining staged, unstaged and untracked work against the prior boundary. Obtain committed facts from the immutable object, not several movable HEAD reads.
Post-commit verification inspects these Git results and hook effects, not routine repetition of product tests. If hooks changed relevant inputs, report which evidence no longer applies; delivery remains stopped on mismatch or uncertain effects.
Exit zero alone is not exact delivery. After any failure, observe HEAD and actual index/worktree effects before classifying the result. Distinguish refusal before execution, Git failure with observed unchanged HEAD, created-commit mismatch and incomplete observation. Even unchanged HEAD cannot rule out hook side effects. An attempted commit or uncertain effects stops delivery without retry, amend, reset, rollback or a repair commit. Preserve the observed state and report gaps; never claim successful delivery when required observations fail or disagree.
Return the result
Concisely report kind and purpose, owner or refs when relevant, commit SHA when observed, delivered paths and message subject; include remaining work and material omissions when present. Retain the complete message and content/history observations as evidence; expand them when requested or needed to explain a mismatch, not as routine output. For a stop, name the missing condition, observed Git effects and safe next action. No stage grants push, tag, publication, deployment, approval, cross-branch integration or history rewrite.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

