Agent skill · software engineering · abhigyanpatwari
gitnexus-lfg
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\".
Why this skill is useful
Adds a structured orchestration for the GitNexus pipeline, integrating planning, execution, and review processes that the AI wouldn't generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-06. 45,147 stars on the source repository.
What this skill does
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. 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/workflowbench/) — 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): 1. Proceed to work — continue to Lane 3. 2. Stop here — the plan file is the deliverable; end the pipeline. Depth was the user's up-front choice in Lane 1, so deepening is not offered by default — but honor an explicit request for it at the gate: run gitnexus-plan Deepen mode on the plan file and return here with the strengthened plan, as many times as the user asks. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills abhigyanpatwari/gitnexus-lfg