Agent skill · software engineering · abhigyanpatwari
gitnexus-work
Use when executing an engineering plan produced by gitnexus-plan (or a small bounded task directly) — implements step by step with GitNexus impact checks before every symbol edit, tests from the plan''s scenarios, and detect_changes gating every commit. Examples: "/gitnexus-work docs/plans/2026-07-11-gitnexus-plan-ingestion-retry.md", "/gitnexus-work" (latest plan), "execute the plan".
Why this skill is useful
Adds executable scripts for verifying and executing engineering plans with GitNexus that are not publicly documented.
What it needs
Requires gitnexus installed locally. About 9k tokens when loaded. Last updated 2026-08-06. 45,147 stars on the source repository.
What this skill does
gitnexus-work — execute a gitnexus-plan Execute an implementation plan produced by gitnexus-plan, shipping it as a sequence of verified, atomic commits. The plan's section 11 (implementationcontext pack) is the primary machine-readable input; the prose sections are its rationale. This skill does edit code — it is the executor counterpart to the planning-only gitnexus-plan. Input triage Plan path (or blank → the newest docs/plans/gitnexus-plan.md under the current repo root): the normal mode; continue to Phase 1. Schema-2 plans have a normalized repo-relative docs/plans/YYYY-MM-DD-gitnexus-plan-<3-5-word-slug>.md generatedplanpath. Resolve only a lexical candidate, then invoke scripts/evidence-provenance.mjs read-plan --repo <root> --generated-plan <candidate> and load only the exact bytes in its descriptor-anchored receipt. Require the receipt's canonical repo-relative path to equal the document's generatedplanpath byte-for-byte; reject an external, escaping, differently scoped, or mismatched value. A plan in another target repo may still be passed by explicit path. If Phase 1's pre-completed check finds every §7 step of the newest plan already landed, stop and ask instead of re-executing it. Bare task text: trivial and bounded (1–2 files, no architectural decisions) → implement directly with the same discipline: impact before every symbol edit, minimal change, tests when behavior changes, verification commands taken from the repo's own scripts (package.json / CI), detectchanges before every commit, and the shared Build-current/index-current procedure before graph-dependent impact and final verification. Anything larger → recommend running /gitnexus-plan first; honor the user's choice if they decline. Phase 1 — Load and re-anchor the plan 1. Resolve the target repo and normalized plan candidate, then invoke this skill's descriptor-anchored scripts/evidence-provenance.mjs read-plan command exactly as specified in references/evidence-provenance.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills abhigyanpatwari/gitnexus-work