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".

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable execution workflow with strong validation gates and progressive disclosure to a real reference and script. The main weakness is repetitive restatement of the same graph-freshness requirements within the Build-current/index-current procedure.

Suggestions

In the Build-current/index-current procedure, state the freshness requirements (status: up-to-date, empty incompleteReasons, runnerIdentityStatus: current) once and reference them from steps 1 and 5 instead of restating near-identical lists.

Consider moving the detailed schemaVersion-4 receipt field enumeration (dependency canonicalization, manifest/lockfile/package-count/digest) into references/evidence-provenance.md, keeping only the acceptance criteria inline.

Tighten Phase 4 step 3, which re-announces 'run the same Build-current/index-current procedure' already established in Phase 2, to a single forward reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of generic-knowledge padding, but the Build-current/index-current procedure restates the same freshness requirements (status: up-to-date, empty incompleteReasons) across steps 1, 5, and the intro, and could be tightened.	3 / 5
Actionability	Provides concrete commands (evidence-provenance.mjs read-plan, node gitnexus/dist/cli/index.js analyze --index-only --pdg, cd gitnexus && npm run build, detect_changes {scope: "staged"}) with only parameterized placeholders as minor gaps.	4 / 5
Workflow Clarity	A clear four-phase sequence with explicit validation checkpoints (impact before edits, detect_changes before commits, rebuild-before-verify), feedback loops (re-anchor on drift, inter-step refresh), and a 'Never' checklist for a destructive/batch operation.	5 / 5
Progressive Disclosure	Well-signaled one-level-deep references to references/evidence-provenance.md and scripts/evidence-provenance.mjs (both real files), with the byte contract pushed to the reference and the executable workflow kept inline.	5 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, explicit 'Use when' trigger, concrete action list, and clear distinction from its planning counterpart. Trigger-term coverage is good but could add a few more natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'implements step by step with GitNexus impact checks before every symbol edit, tests from the plan''s scenarios, and detect_changes gating every commit' — giving comprehensive coverage of what the executor does.	5 / 5
Completeness	Explicitly answers both what (step-by-step implementation with impact checks, tests, detect_changes gating) and when ('Use when executing an engineering plan produced by gitnexus-plan'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural invocation examples ('/gitnexus-work docs/plans/...', '/gitnexus-work', 'execute the plan') and 'engineering plan' phrasing, but offers limited synonyms beyond the gitnexus-specific terms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche as 'the executor counterpart to the planning-only gitnexus-plan', with distinct invocation triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: abhigyanpatwari/GitNexus
Path: .claude/skills/gitnexus-work/SKILL.md
Commit: 4e51213

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.