source-custody
Skill2 starsChanged 4 days agoApache-2.0View on GitHub
Protect concurrent Git work using normal Git tooling.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-orchestrationSkill
- change-aware-verificationSkill
- context-continuitySkill
- execution-intent-preservationSkill
- independent-engineering-reviewSkill
- observable-progressSkill
- outcome-driven-engineeringSkill
- prototype-firstSkill
- repair-and-resumeSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 13
Use distinct branches/worktrees for independent tasks.
- Distinctive: line 14
Never overwrite another worker's changes or discard unique work.
- Distinctive: line 15
Check real GitHub state before retrying uncertain push or PR creation.
≈ “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
Source Custody
Objective
Protect concurrent Git work using normal Git tooling.
Practice
- Inspect actual branch, HEAD and dirty state before editing.
- Use distinct branches/worktrees for independent tasks.
- Never overwrite another worker's changes or discard unique work.
- Check real GitHub state before retrying uncertain push or PR creation.
- Keep exact repository/branch/worktree/HEAD and worker/session ownership in the issue claim and closeout handoff for verified private repositories. For public/unknown visibility use the literal withheld worktree field and restricted exact local custody record required by
policies/ISSUE_LIFECYCLE.md; pass exact source privately to the worker and retain it across resumption/retirement. Never publish local paths, host details, native identifiers or private evidence in public comments/PRs, including collapsed details. Missing custody preserves source; unsupported attribution stays unknown. Distinguish disposable task source from shared or manually maintained source. - On finished work, hand retirement to the coordinator after worker/process exit using ISSUE_LIFECYCLE.md and the effective worktree-retirement playbook. Never remove an active, dirty, unmerged or resumable checkout; preserve every unique commit/edit and dependent user's source. GitHub remote-branch deletion proves nothing about local safety.
Guidance only. Do not introduce new Graph services, approval gates or required reviewer loops.
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.