commit-workspace-changes
Skill4 starsChanged 2 months agoMITView on GitHub
Validate and commit task-related changes across Git repositories and submodules. Use for local commits or as the commit phase of PR Completion; the calling workflow owns pushing and landing.
In this repository3 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create validated, task-scoped commits and return to the caller.
- Distinctive: line 15
Commit normally. If a hook changes files, inspect and restage only intended changes.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Commit Workspace Changes
Create validated, task-scoped commits and return to the caller. A commit request does not independently authorize publishing or merging. When called by PR Completion, continue there without recursively invoking another lifecycle.
- Reuse the caller's repository/branch inventory, or discover ownership from Git metadata. Snapshot staged, unstaged, untracked changes and active Git operations. Read applicable instructions; preserve unrelated work and intentional staging.
- Resolve in-scope conflicts with
$pr-completion:merge-conflict-resolution. Process changed submodules before parents. Derive the intended branch rather than committing blindly from detached HEAD. - Derive required validation from repository instructions, hooks and CI. Reuse successful evidence for the same tree and scope. Run focused checks and every mandated check not already covered. Do not duplicate a broad check solely because a helper handoff occurred.
- Fix task-caused failures and inspect formatter output. Rerun failed/invalidated checks. Diagnose pre-existing, environment or unrelated failures with evidence; do not loop unchanged commands, weaken tests, bypass hooks, or claim unsupported flakiness.
- Re-read status and staged diff. Stage explicit intended paths; exclude secrets, conflict markers, artifacts and unrelated edits. Split commits only where independent concerns or repository convention warrant it. Infer message style and use DCO sign-off when required.
- Commit normally. If a hook changes files, inspect and restage only intended changes. Verify the new commit and remaining worktree; do not make empty commits. Commit a parent gitlink only when it belongs to the task.
Return repository, commit, validation evidence and remaining changes/blockers concisely. The lifecycle owner handles pushing, PRs, reviews and landing.
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.