Gitnexus Lfg
Use when the user wants the GitNexus engineering pipeline run end-to-end on a task...
Install
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-lfg -g -a claude-code -y- Repository
- abhigyanpatwari/GitNexus48.2k
- Category
- Engineering
- Updated
- 3d ago
- License
- See repository
- Context cost
- Lightabout 1,010 tokens
- Runs scripts
- No, instructions only
What it does
Use when the user wants the GitNexus engineering pipeline run end-to-end on a task: gitnexus-plan (plan depth chosen up front), a blocking gate to execute with gitnexus-work or stop, finishing with a gitnexus-review of the result. Examples: \"/gitnexus-lfg Add retry support to the ingestion pipeline\", \"run the gitnexus pipeline on this\", \"plan, build and review this feature\".
gitnexus-lfg, plan → gate → work → review
Thin orchestrator over three existing skills. It adds no engineering logic of
its own, it sequences gitnexus-plan, gitnexus-work, and
gitnexus-review, with the user deciding at the plan gate. Run every lane
by actually invoking the named skill (read its SKILL.md and follow it);
never inline a summary of what the skill would have done.
/gitnexus-lfg <task description>
/gitnexus-lfg docs/plans/<existing-plan>.md # skip lane 1, start at the gate
Lane 1, Plan
Boundary triage first. If the task is plainly below the planning
boundary, trivial or small-bounded work an agent finishes in well under ~35
turns (the measured regime where a planning pass costs more than it returns;
measured in the GitNexus repository's eval/workflow_bench/), say so and
offer gitnexus-work direct mode as an alternative to the full pipeline
before spending the plan lane. Honor the user's choice.
The threshold is a promoted benchmark policy measured offline, not a timeless heuristic, never self-edit it from a live task. Its re-evaluation governance lives in this skill's README.
Otherwise invoke gitnexus-plan with the task (knob overrides pass through
verbatim; gitnexus-plan owns the up-front depth question, never ask it
again here). If the input is already a plan file path, skip to Lane 2. The
plan lands in docs/plans/, record its path; every later lane consumes it.
Lane 2, The plan gate (user choice, blocking)
Present the plan's chat summary (objective, proposed changes, sequence, top
risks, open questions, plan path), then ask the user, as a blocking
question (AskUserQuestion in Claude Code; a numbered list in chat on CLIs
without a blocking tool):
- Proceed to work, continue to Lane 3.
- Stop here, the plan file is the deliverable; end the pipeline.
