GitNexus/gitnexus-claude-plugin/skills/gitnexus-work
Gergő Magyar 6088d2e309
Some checks are pending
CodeQL / Analyze (javascript-typescript) (push) Waiting to run
CodeQL / Analyze (python) (push) Waiting to run
Gitleaks / gitleaks (push) Waiting to run
Publish / Classify release event (push) Waiting to run
Publish / RC guard (marker + release-PR skip) (push) Blocked by required conditions
Publish / ci (push) Blocked by required conditions
Publish / Publish to npm (push) Blocked by required conditions
Publish / Build & Push RC Docker images (push) Blocked by required conditions
Scorecard / Scorecard analysis (push) Waiting to run
Skill copy sync / shipped skills drift guard (push) Waiting to run
Trivy Image Scan / Trivy (gitnexus-cli) (push) Waiting to run
Trivy Image Scan / Trivy (gitnexus-web) (push) Waiting to run
chore: release v1.6.10 (#3064)
* chore: release v1.6.10

* fix(eval): derive the pinned runtime version from package.json

The containment suite mounts a GitNexus runtime built from this checkout and
asserts its version equals PINNED_GITNEXUS_VERSION, a constant hardcoded to
"1.6.9" when the harness landed in #2566. The first release after that lands
1.6.10 in gitnexus/package.json, the built runtime reports 1.6.10, and
`eval / containment (ubuntu)` fails on drift the release itself created.

Read the version from gitnexus/package.json instead. The check keeps its real
job -- proving the mounted runtime came from this checkout rather than a
published package -- without a copy that only ever drifts on release day.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Gergo Magyar <gergomagyar0@gmail.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-27 23:21:40 +01:00
..
references fix(skills): publish gitnexus-plan artifacts on macOS without an interpreter (#2905) (#2922) 2026-08-11 12:24:53 +01:00
scripts fix(skills): publish gitnexus-plan artifacts on macOS without an interpreter (#2905) (#2922) 2026-08-11 12:24:53 +01:00
mcp.json chore: release v1.6.10 (#3064) 2026-08-27 23:21:40 +01:00
README.md feat(skills): GitNexus Engineering Tool Kits (#2566) 2026-07-19 15:07:24 +01:00
SKILL.md fix(mcp): stop scaling the detect_changes query with the diff's hunk count (#2915) (#2930) 2026-08-12 14:51:17 +01:00

gitnexus-work — execute a gitnexus-plan

The executor counterpart to gitnexus-plan: consumes a plan's §11 implementation context pack and ships it as verified atomic commits, with GitNexus discipline baked in — impact before every symbol edit, detect_changes before every commit, tests from the plan's scenarios, and a two-layer drift check that re-anchors both commit and dirty working-tree evidence before relying on it.

Invocation

CLI How to invoke
Claude Code /gitnexus-work [plan path] (blank → newest docs/plans/*gitnexus-plan*.md in this repo)
Codex CLI Ask: "run gitnexus-work on " (Codex reads AGENTS.md), or install the skill user-level (below)

Codex (user-level install)

cp -r .claude/skills/gitnexus-work ~/.agents/skills/gitnexus-work

Optionally, for an explicit slash command, create ~/.codex/prompts/gitnexus-work.md:

---
description: Execute a gitnexus-plan as verified atomic commits (impact-checked, detect_changes-gated)
argument-hint: <plan path, or blank for the newest plan>
---

Use the gitnexus-work skill for: $ARGUMENTS

Read `~/.agents/skills/gitnexus-work/SKILL.md` (prefer the repo copy at
`.claude/skills/gitnexus-work/SKILL.md` when present) and follow its phases in
order. This skill edits code; honor its impact-before-edit and
detect_changes-before-commit rules without exception.

Contract with gitnexus-plan

  • Input: the 13-section plan document; §11's implementation_context fields are the machine-readable interface (see ../gitnexus-plan/references/context-pack.md for the stability contract).
  • evidence_provenance is mandatory in compact and full plans. Work always loads the plan only through its byte-identical helper's descriptor-anchored read-plan command, consumes the exact base64 bytes from that receipt, and recomputes the global dirty digest and sorted cited-path manifest even at the same HEAD. Schema-2 generated_plan_path is a normalized repo-relative docs/plans/<date>-gitnexus-plan-<slug>.md path; external, escaping, or differently scoped values are invalid. It must also equal the read receipt's canonical target-repo-relative path byte-for-byte. Missing or schema-1 evidence re-anchors under schema 2.
  • The plan is never mutated; deviations are recorded in commit messages and the final report.
  • Changed citations are re-read, new uncited dirty paths are assessed for scope, and unreadable evidence blocks dependent work. Deepen is reserved for drift that invalidates scope, requirements, a key technical decision, or the planned seam.

Graph freshness

One fail-closed Build-current/index-current procedure runs before every graph-dependent impact query and again before final graph verification. It compares indexed commit and the schema-4 runner identity (including its gitnexus-analyzer-dependency-runtime-v4 dependency payload/runtime digest), requires no incomplete-index recovery markers, invalidates on relationship-affecting committed or uncommitted edits, builds and invokes the current local analyzer with PDG indexing when needed, and treats timestamps only as a conservative trigger. Build, refresh, or identity failures block impact and completion; the executor never falls back to a stale runner.