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

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/gitnexus-work/SKILL.md

Quality

Content

73%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.

A well-structured, actionable execution workflow with strong validation gates and clear sequencing. The main weakness is verbosity from repeating the same procedure and constraints across phases, and some detailed content that could live in a reference file.

Suggestions

Factor the full Build-current/index-current procedure into its own reference file and reference it by name from Phase 2 and Phase 3 to remove repeated inline detail.

Consolidate the repeated drift-check and re-anchor constraints so each rule is stated once and cross-referenced rather than restated per phase.

Tighten the dense provenance paragraphs in Phase 1 by moving command-form details to references/evidence-provenance.md and keeping only the binding rules inline.

Dimension	Reasoning	Score
Conciseness	It avoids explaining basic concepts Claude already knows, but restates the Build-current/index-current procedure and drift constraints multiple times across phases; it is mostly efficient yet could be tightened.	3 / 5
Actionability	Provides concrete executable commands — 'scripts/evidence-provenance.mjs read-plan --repo <root> --generated-plan <candidate>', 'node gitnexus/dist/cli/index.js analyze --index-only --pdg', 'detect_changes {scope: "staged"}' — with minor gaps where values are parametric.	4 / 5
Workflow Clarity	A clearly sequenced four-phase workflow with abundant explicit validation checkpoints (drift check, re-anchor, impact-before-edit, detect_changes-before-commit, final verification) and feedback loops (route back to gitnexus-plan Deepen mode on structural miss).	5 / 5
Progressive Disclosure	References to references/evidence-provenance.md and scripts/evidence-provenance.mjs are clearly signaled, real, and one level deep; however the Build-current procedure is fully inlined rather than split out, a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

83%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.

A strong description that clearly states what the skill does and when to use it, with concrete trigger examples. The main weakness is jargon-dense phrasing that slightly limits accessibility of the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists several 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' — but the actions are densely jargon-bound, just short of comprehensive clarity.	4 / 5
Completeness	Explicitly answers both — 'Use when executing an engineering plan produced by gitnexus-plan (or a small bounded task directly)' gives the when, and the action list gives the what, with concrete example trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('execute the plan', '/gitnexus-work', example invocations with plan paths), giving good keyword coverage, though a few common phrasings are absent.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche as 'the executor counterpart to the planning-only gitnexus-plan', but the 'small bounded task directly' mode introduces minor overlap risk with general coding skills.	4 / 5
	Total	17 / 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: c6b2416

Reviewed: 2 days 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.