tidy-commit-push
Skill2 starsChanged 40 days agoMITView on GitHub
Inspect git status, remove junk/legacy/secrets from the commit set, craft a conventional commit message, and commit locally; push only with explicit user approval. Use before shipping a logical unit of work. Triggers: tidy commit, conventional commit, pre-push hygiene, commit and push.
- Reads credentials
- Commits and pushes
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-auditSkill
- agentic-reactorSkill
- agent-orchestratorSkill
- ai-optimizationSkill
- architecture-synthesisSkill
- audit-allow-buildsSkill
- audit-ide-dependenciesSkill
- author-workflow-skillSkill
- bdd-strategizerSkill
- chrome-extension-mv3Skill
- concurrent-cli-agentsSkill
- control-feederSkill
- control-graphSkill
- cursor-transcript-harvestSkill
- cv-promote-guardSkill
- devcontainer-hardenedSkill
- dual-copy-skill-publishSkill
- explore-repo-readonlySkill
- finder-reactorSkill
- fix-dependency-securitySkill
- fusion-sageSkill
- git-worktreesSkill
- grok-host-prepSkill
- gt-flowSkill
- higher-order-decision-architectSkill
- looperSkill
- master-plannerSkill
- mvu-refactor-planSkill
- odysseus-navigatorSkill
- project-editor-profileSkill
- react-client-expertSkill
- semantic-markup-cssSkill
- semantic-nameSkill
- session-unit-orderSkill
- shell-kernel-ontologySkill
- skill-rename-propagationSkill
- split-to-prsSkill
- src-tree-reorganizeSkill
- stellar-roadmapSkill
- stellar-spacemapSkill
- subagent-delegationSkill
- subagent-explore-reportSkill
- supply-chain-hardenSkill
- tauri-agenticSkill
- tauri-ipc-debugSkill
- upgrade-packagesSkill
- verification-cockpitSkill
- x-agent-resourcesSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 56
Remove legacy paths only if intentional delete is part of the change
- Distinctive: line 57
Privacy: no tokens/keys; if staged → git restore --staged and scrub
- Very specific: line 58
Prefer git add <paths> over blind git add .
≈ “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
tidy-commit-push
Load rule: Formal SoT. Compose with agent-orchestrator report and split-to-prs for multi-PR ships.
CLT: ../rules/clt-dual-load.mdc — push HITL = exact preview (extraneous ↓) + real approval (germane).
// Axioms
A1 Never commit .env, credentials, private keys, large binaries by accident
A2 One logical change per commit (or explicit multi-commit plan)
A3 Push = HITL — only with user approval on shared remotes / protected branches
A4 Prefer HEREDOC commit messages; match repo history style (git log -5)
A5 Never --force to main/master unless explicit disaster recovery + approval
A6 Evaluate(δ) ≔ (C, E, η)Use / skip
| Use | Skip |
| ready to record a coherent unit | WIP still broken with no message yet |
| pre-PR hygiene | user said do not commit |
| after agent wave | secrets present and unredacted |
Procedure
1 Inspect → 2 Tidy stage → 3 Message → 4 Commit → 5 Push? (HITL) → 6 PR? (HITL)1. Inspect
git status
git diff
git diff --staged
git log -5 --oneline
git branch -vv2. Tidy staging set
- Unstage junk:
*.log,node_modules, build outs, editor swap - Remove legacy paths only if intentional delete is part of the change
- Privacy: no tokens/keys; if staged →
git restore --stagedand scrub - Prefer
git add <paths>over blindgit add .when mixed worktrees
3. Message
Conventional if repo uses it: type(scope): summary
Types: feat fix chore docs refactor test perf
4. Commit (local default)
git commit -m "$(cat <<'EOF'
type(scope): short summary
Optional body — why, not how.
EOF
)"5. Push — only if user requested
git push -u origin HEAD
# never --force to main/master unless explicit disaster recovery + approval6. PR — only if requested: gh pr create …
Done when
git statusclean or only intentional leftovers listed- Commit exists with accurate message
- Push/PR only per user request
Anti-patterns
| ¬ | Do |
| commit + push secrets | scrub; rotate if leaked |
| "WIP" on main without ask | feature branch |
| amend published commit | new commit |
| force-push shared branch | recover with user plan |
| silent agent push | wait for HITL |
Related: agent-orchestrator · split-to-prs · git-worktrees
Done_when cmds: git status -sb · git log -1 --oneline · (optional) git push only after confirm.
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.

