gitnexus-work

Executes gitnexus-plan implementation plans as verified atomic commits with graph-based impact checks.

1|Updated Jul 27, 2023
One-click install
npx skills add https://github.com/AlexTheGuitarGuy/.dotfiles --skill gitnexus-work-alextheguitarguy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-work
Source: https://github.com/AlexTheGuitarGuy/.dotfiles/tree/main/claude/.claude/skills/gitnexus-work
Command: npx skills add https://github.com/AlexTheGuitarGuy/.dotfiles --skill gitnexus-work-alextheguitarguy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Turning a written engineering plan into code often drifts from the plan, skips verification, or lands as one unreviewable mega-commit. This Skill executes a gitnexus-plan document step by step, enforcing impact analysis before every symbol edit and change detection before every commit. ## Core Features & Use Cases - Plan-driven execution: Loads the plan's machine-readable implementation context (acceptance criteria, files to modify, tests, verification commands) and works through its steps in order, one conventional commit per step. - Drift re-anchoring: Recomputes evidence provenance digests against the current working tree, re-reads changed cited files, and blocks work when evidence is unreadable or scope is invalidated. - Graph-gated safety: Runs a build-current/index-current freshness procedure before every GitNexus impact query and gates every commit on detect_changes so unexpected affected flows are investigated first. - Use Case: After generating a plan with gitnexus-plan, run "/gitnexus-work docs/plans/2026-07-11-gitnexus-plan-ingestion-retry.md" to ship it as tested, atomic commits with a final Definition-of-Done report. ## Quick Start Ask the AI to run /gitnexus-work on your latest plan file, or pass a specific plan path, and it will implement the plan step by step with verified commits.

Frequently Asked Questions about gitnexus-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute a gitnexus-plan implementation plan?▼

Run /gitnexus-work with the plan path, or with no argument to pick the newest docs/plans/*gitnexus-plan*.md file. The skill loads the plan's section 11 implementation context, then implements each step with impact checks, tests, and one atomic commit per step.

How to implement a plan as atomic commits with verification?▼

The skill works through the plan's step sequence, running the plan's verification commands per step and gating every commit on a detect_changes check that confirms only expected symbols and flows changed. Each commit leaves the tree coherent, so work can stop after any step.

Can gitnexus-work handle small tasks without a plan?▼

Yes, bare task text that is trivial and bounded (1-2 files, no architectural decisions) is implemented directly with the same discipline: impact before edits, tests when behavior changes, and detect_changes before commits. Larger tasks are routed back to gitnexus-plan first.

What happens when the working tree has drifted from the plan?▼

The skill recomputes the global dirty digest and cited-path manifest even at the same HEAD, re-reads changed cited files, and assesses new uncited dirty paths for scope overlap. Unreadable evidence blocks dependent work; drift invalidating scope or key decisions routes back to plan Deepen mode.

Why does gitnexus-work refuse to run an impact query sometimes?▼

Impact queries require a fresh knowledge graph proven by the build-current/index-current procedure, which checks the indexed commit, runner identity receipt, and incomplete-index markers. Any build, refresh, or identity-verification failure blocks graph-dependent work rather than falling back to a stale index.

What are the limitations of gitnexus-work?▼

It never edits the plan body, never expands scope beyond the plan's deferred follow-ups, and never commits without the detect_changes gate. The evidence provenance helper only supports Linux and macOS platforms with no-follow descriptor anchoring; other platforms fail closed.