aio-commit
Skill0 starsChanged 30 days agoMITView on GitHub
Create a focused local commit after inspecting owned backend changes and validation evidence.
In this repository54 other files it gives its agents.
- agent-workflowsSkill
- aio-agentsSkill
- aio-algorithmsSkill
- aio-apiSkill
- aio-architectureSkill
- aio-autoplanSkill
- aio-benchmarkSkill
- aio-brainstormSkill
- aio-canarySkill
- aio-checkpointSkill
- aio-ciSkill
- aio-compoundSkill
- aio-dataSkill
- aio-debugSkill
- aio-devex-reviewSkill
- aio-doc-reviewSkill
- aio-explainSkill
- aio-feedbackSkill
- aio-handoffSkill
- aio-ideateSkill
- aio-observeSkill
- aio-optimizeSkill
- aio-pipelinesSkill
- aio-plan-reviewSkill
- aio-planSkill
- aio-proofSkill
- aio-prototypeSkill
- aio-qa-onlySkill
- aio-qaSkill
- aio-releaseSkill
- aio-resumeSkill
- aio-reviewSkill
- aio-securitySkill
- aio-shipSkill
- aio-simplifySkill
- aio-specSkill
- aio-tddSkill
- aio-test-auditSkill
- aio-testSkill
- aio-verifySkill
- aio-workSkill
- aio-worktreeSkill
- all-in-oneSkill
- apple-appstore-reviewerSkill
- backend-algorithmsSkill
- backend-debugSkill
- backend-pipelinesSkill
- backend-planSkill
- backend-reviewSkill
- backend-verifySkill
- complete-destructionSkill
- launch-readinessSkill
- play-policy-insightsSkill
- reverse-engineer-anythingSkill
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 a focused local commit after inspecting owned backend changes and validation evidence.
- Distinctive: line 14
Check relevant test evidence is for the current source and inspect whitespace/conflict checks.
≈ “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
AIO Commit
Create a focused local commit after inspecting owned backend changes and validation evidence.
Protocol
- Confirm the intended repository/worktree, branch and owned files. Inspect status/diff and preserve unrelated user changes; never stage an ancestor home repository by accident.
- Review the selected diff for secrets, generated/scratch files, conflicts and consistency with acceptance. Include required source/tests/docs/migrations as one coherent change.
- Check relevant test evidence is for the current source and inspect whitespace/conflict checks. Preserve intentionally unchanged vendored files and disclose upstream formatting warnings separately.
- Inspect the index before staging. Preserve unrelated staged user changes and use a path-limited commit, such as
git commit --only -- <owned-paths>, when needed to keep them out of this commit. Commit with a problem/result-oriented message and inspect its exact file set plus remaining status; a local commit does not imply push, PR or deployment.
Return and handoff
An observed local commit ID, owned scope, validation and remaining working-tree state.
In a pipeline, use the stage contract and return to the integrating controller. Run only this specialist's owned scope; preserve the user's accepted decisions and existing authorization.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

