recallnet
- 8 skills
- 0 followers
- last month last updated
- ▌ Context Diff 2 · recallnetCheck which @context annotations are affected by recent code changes. Use after editing code to verify context accuracy and flag stale annotations.
- ▌ Context Diff · recallnetCheck which @context annotations are affected by recent code changes. Use after editing code to verify context accuracy and flag stale annotations.
- ▌ Worktree · recallnetWork in a dedicated Git worktree, make all commits there, and land changes through `mq` instead of merging directly into `main`. Use after onboarding, once the user already understands the repo's setup and wants the contribution workflow.
- ▌ Onboarding · recallnetFirst skill for new contributors, fresh clones, and setup questions in the mainline repo. Separates developing mainline from using mq on another repo, verifies the local baseline, explains canonical-root trust, and clarifies which commands should or should not work in this source checkout.
- ▌ Goal Planner · recallnetPlan and file goals and feature issues through conversation. Use when the user wants to create goals, plan features, file issues, or discuss what to build next.
- ▌ Codecontext Setup · recallnetSet up or repair codecontext adoption in a project. Use this whenever the user wants to add @context annotations to a repo, install the codecontext toolchain, update AGENTS.md guidance, improve agent workflows around decision capture, or audit whether an existing codecontext setup is coherent. Prefer this skill over vague "document the tool" work: it is specifically for making a repo actually usable with codecontext.
- ▌ Context Scope · recallnetSurface @context annotations before editing a file. Shows critical constraints, tradeoffs, and risks sorted by priority. Use when about to modify unfamiliar or complex code, or when the user asks what constraints apply to a file.
- ▌ Context Staged · recallnetCheck all staged files for stale @context annotations before committing. Use as a pre-commit verification step.