skills.rest
abhigyanpatwari
abhigyanpatwariCOMMUNITY
Explore all skills by this author →
GitHub

gitnexus-work

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

46.8k|5.1k|Updated Aug 2, 2025
Search Tags:#plan execution#impact analysis#atomic commits#Git Workflow#GitNexus#Code Implementation#Knowledge Graph
One-click install
npx skills add https://github.com/abhigyanpatwari/GitNexus --skill gitnexus-work
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-work
Source: https://github.com/abhigyanpatwari/GitNexus/tree/main/gitnexus-claude-plugin/skills/gitnexus-work
Command: npx skills add https://github.com/abhigyanpatwari/GitNexus --skill gitnexus-work

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Executing a multi-step engineering plan by hand risks missed dependencies, broken call chains, and unverified commits. This Skill turns a gitnexus-plan document into a disciplined execution run: every symbol edit is preceded by a knowledge-graph impact query, every commit is gated by change detection, and plan evidence is re-anchored against the current working tree before it is trusted.

Core Features & Use Cases

  • Plan-driven execution: Loads a gitnexus-plan's section 11 implementation context pack (acceptance criteria, primary symbols, tests, verification commands) and works through its steps in order, committing atomically per step.
  • Graph freshness enforcement: Runs a build-current/index-current procedure before every impact query and final verification, refusing to rely on stale GitNexus indexes or legacy runner identities.
  • Two-layer drift detection: Recomputes dirty-tree digests and cited-path manifests via the evidence-provenance helper, re-reading changed citations and blocking on unreadable evidence.
  • Use Case: After generating a plan with gitnexus-plan for a refactor, run "/gitnexus-work docs/plans/2026-07-11-gitnexus-plan-ingestion-retry.md" to implement each step with impact checks, scenario-derived tests, and detect_changes-gated commits.

Quick Start

Ask the agent to run /gitnexus-work on your latest plan file, or invoke it with no argument to execute the newest plan under docs/plans.

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?▼

Invoke /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 context pack, re-anchors its evidence, then implements each step with impact checks and gated commits.

What is the difference between gitnexus-plan and gitnexus-work?▼

gitnexus-plan produces the 13-section planning document with a machine-readable implementation context pack; gitnexus-work is the executor that consumes that pack and ships it as verified atomic commits. The plan is never mutated during execution.

Can gitnexus-work run a small task without a plan?▼

Yes, bare task text is supported for trivial bounded changes of one to two files with no architectural decisions. Larger tasks trigger a recommendation to run gitnexus-plan first, though the user's choice to proceed directly is honored.

Why does gitnexus-work block on stale GitNexus indexes?▼

Impact queries against a stale knowledge graph can miss dependents and break call chains. The build-current/index-current procedure rebuilds and re-indexes when the runner identity or commit is stale, and any failure blocks graph-dependent work rather than falling back to old data.

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

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

Related Skills

Explore More Software Engineering Skills→
learnzdevelopmenthublearnzdevelopmenthub
1

dev-test

Generate test plans and placeholder stubs from acceptance criteria.

Community
Advanced
FerroxLabsFerroxLabs
21

ferrox-pr-branch

Create a pull-request branch by filtering out .planning commits.

Community
Intermediate
raybirdraybird
1

gitnexus-guide

Document GitNexus knowledge graph queries and MCP tool operations.

Community
Intermediate
SkogAISkogAI
1

requesting-code-review

Dispatch the code-reviewer subagent to review code changes against plan and requirements.

Official
Basic