astrobyte-recall
Skill1 starsChanged 14 days agoMITView on GitHub
Reconstruct current work state from repository evidence, handoffs, decision trails, recent history, artifacts, and available session records. Use when resuming work, switching harnesses, changing machines, or asking where a project was left.
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/adopt-skill-stack.mdcCursor rule
- adopt-skill-stackSkill
- api-and-interface-designSkill
- astrobyte-architectSkill
- astrobyte-git-identitySkill
- astrobyte-modeSkill
- astrobyte-project-startupSkill
- astrobyte-pr-workflowsSkill
- astrobyte-reviewSkill
- astrobyte-show-workSkill
- astrobyte-tddSkill
- astrobyte-verify-projectSkill
- blast-radiusSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- codebase-designSkill
- continual-improvement-checkSkill
- deprecation-and-migrationSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- frontend-designSkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- grillingSkill
- handoffSkill
- hermetic-test-suitesSkill
- observability-and-instrumentationSkill
- performance-optimizationSkill
- pr-feedback-loopSkill
- prototypeSkill
- researchSkill
- security-and-hardeningSkill
- setup-astrobyte-skillsSkill
- shipping-and-launchSkill
- source-driven-developmentSkill
- technical-writingSkill
- to-questionnaireSkill
- typescript-best-practicesSkill
- unslopSkill
- update-skill-stackSkill
- writing-for-agentsSkill
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 10
Read repository instructions and current Git state.
- Distinctive: line 12
Use harness session or thread history when available.
- Distinctive: line 13
Verify claimed running processes, files, artifacts, tests, metrics, and remote state before relying on them.
≈ “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
Astrobyte recall
- Read repository instructions and current Git state.
- Inspect recent commits, active branches or worktrees, open changes, project handoffs,
.astrobyte/decisions.tsv, run state, and generated next-step prompts. - Use harness session or thread history when available. Treat it as evidence that may be stale.
- Verify claimed running processes, files, artifacts, tests, metrics, and remote state before relying on them.
- Separate facts, likely inferences, and unresolved questions.
Return:
- objective
- completed and verified work
- current live state
- decisions and rationale
- uncommitted or external state
- blockers and risks
- exact next safe action
- evidence locations
Recall is complete when another agent can continue without repeating completed work or trusting stale transcript claims.
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.