context-handoff
Skill0 starsChanged 13 days agoMITView on GitHub
Create a reliable handoff note so another engineer or coding agent can continue work without redoing exploration. Use before switching sessions, handing off a long task, or pausing midway.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- hatemecha/skillstheir own version, first seen Nov 1, 2026
- timyeou1234/context-handofftheir own version, first seen Nov 1, 2026
- asta-nguyen/kamehadbtheir own version, first seen Oct 16, 2026
- vorteg/swagenticstheir own version, first seen Oct 13, 2026
- yuanJewel/skillstheir own version, first seen Oct 11, 2026
- Gaurav890/everything-agentic-engineeringtheir own version, first seen Sep 13, 2026
Used with
Projects with it also use systematic-debugging.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillsystematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Also in 3 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- asta-nguyen/kamehadb★ 14same name
- asta-nguyen/agent-devkit★ 4same name
- timyeou1234/context-handoff★ 2same name
- yuanJewel/skills★ 2same name
- Gaurav890/everything-agentic-engineering★ 1same name
- newyounghe-design/context-handoff-skill★ 1same name
- SuperMate-Ai/SuperMate-Harness-System★ 1same name
- vorteg/swagentics★ 1same name
- aimasteracc/harness-kit★ 0same name
- djhyes/context-handoff★ 0same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-skill-auditSkill
- api-contract-checkSkill
- build-rescueSkill
- change-narrativeSkill
- data-quality-gateSkill
- dataset-workshopSkill
- dependency-careSkill
- docs-syncSkill
- experiment-ledgerSkill
- failure-forensicsSkill
- model-diff-reviewSkill
- model-eval-designSkill
- multi-agent-crosscheckSkill
- parallel-task-designSkill
- performance-proofSkill
- release-readinessSkill
- repo-scoutSkill
- research-evidence-mapSkill
- review-lensSkill
- safe-migrationSkill
- security-surfaceSkill
- spec-firstSkill
- sql-integrity-checkSkill
- test-driven-changeSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
4
Distinctive
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 16
Keep it short enough to rehydrate quickly.
- Distinctive: line 28
Never claim work was saved or committed if it was not.
- Distinctive: line 29
Never include credentials, tokens, private user data, or unnecessary personal information in the handoff.
- Distinctive: line 30
If repository state changed outside the agent's knowledge, tell the next agent to inspect status before editing.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Context Handoff
Procedure
- Summarize the user's goal and the acceptance criteria; keep requirements separate from assumptions.
- Record the current repository and branch, relevant files, important symbols, current diff status, and any uncommitted user work.
- List commands run and exact outcomes. Clearly distinguish tested facts, inferred explanations, and open hypotheses.
- Note decisions made and alternatives rejected with brief reasons. Include links or paths to source evidence where possible.
- Describe remaining work in a prioritized order, with a concrete next action rather than generic reminders.
- Record safety boundaries: files/data not to modify, external actions not yet authorized, secrets to avoid, and any concurrent work or shared resource constraints.
- Keep it short enough to rehydrate quickly; link detailed logs instead of pasting them.
Template
- Goal / acceptance criteria
- Current state
- Files and key decisions
- Verification performed
- Remaining work (ordered)
- Risks / unknowns
- Safe next command or action
Boundaries
- Never claim work was saved or committed if it was not.
- Never include credentials, tokens, private user data, or unnecessary personal information in the handoff.
- If repository state changed outside the agent's knowledge, tell the next agent to inspect status before editing.
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.