Manages saved implementation plans attached to git branches via Branch Memory.
npx skills add https://github.com/nseng-ai/ns --skill branch-context-nseng-ai
Please help me install this Agent Skill. Skill: branch-context Source: https://github.com/nseng-ai/ns/tree/main/skills/incubating/branch-context/branch-context Command: npx skills add https://github.com/nseng-ai/ns --skill branch-context-nseng-ai
branch-context namespace contract. - Diagnostics and repair: Inspect saved-plan stores and attached-plan entries with deterministic CLI helpers, recover from stale or orphaned plan state, and resolve ambiguous keys. - Plan administration: Retarget a saved plan to a different source branch, move or copy plans between branches, and handle collisions with explicit destructive-intent safeguards. - Use Case: You saved an implementation plan while on main, then created a feature branch. Use this skill family to attach the plan as branch context, later load it in a fresh session, and implement directly from the attached plan. ## Quick Start Ask the agent to inspect the branch-context entries attached to the current branch and load the attached implementation plan.High-intent search queries and answers about installing and using this skill.
Use the branch-context-from-plan step skill or `ns branch-context exec from-plan`, which creates the branch and attaches the saved plan as a Branch Memory entry keyed `<branch-context-slug>.md`. The plan is resolved from the local plan store before attachment.
A saved plan is a Markdown file in the machine-local plan store written before a branch exists. An attached plan is the canonical plan stored in the Branch Memory `branch-context` namespace on the target branch, used for implementation.
Saved plans live under `$XDG_STATE_HOME/ns/enriched-plan/<repo>/<encoded-source-branch>/<slug>.md`, defaulting to `$HOME/.local/state/ns/enriched-plan/`. Branch slashes are encoded as `---` in the path segment.
Yes, retargeting moves the saved plan to the target source-branch directory after checking for path collisions. The skill stops unless replacement intent is explicit, updates only obvious metadata lines, and reports old and new paths.
The default safety posture refuses collisions with existing files, branches, and Branch Memory entries unless the user gives explicit destructive intent. This prevents accidental loss of attached plans or branch state.
Do not use it for generic planning, branch creation, or implementation without explicit branch-context intent, nor as a substitute for the step skills that own specific create or implement commands. It is the shared reference and diagnostics layer.
yz0812Automate code review for repository changes and write markdown reports.
VIPER-MetricsImplement approved feature plans using git worktrees and phased execution.
diy-accounting-ukCatalogue repository state and merge pull requests that pass all readiness gates.
herren-officialSave the current implementation plan to .claude/plan/{branch}-plan.md.