gitnexus-lfg

Orchestrates plan, gate, work, and review lanes across GitNexus engineering skills.

46.8k|5.1k|Updated Aug 2, 2025
One-click install
npx skills add https://github.com/abhigyanpatwari/GitNexus --skill gitnexus-lfg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-lfg
Source: https://github.com/abhigyanpatwari/GitNexus/tree/main/gitnexus-claude-plugin/skills/gitnexus-lfg
Command: npx skills add https://github.com/abhigyanpatwari/GitNexus --skill gitnexus-lfg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gitnexus.

What problem does it solve?

Running a full engineering change end-to-end requires coordinating planning, execution, and review steps that are easy to skip or do out of order, leading to unplanned edits and unreviewed commits. This Skill sequences the GitNexus plan, work, and review skills into one pipeline with a blocking user gate before any code is written.

Core Features & Use Cases

  • Pipeline Orchestration: Invokes gitnexus-plan, gitnexus-work, and gitnexus-review in order, passing the plan file path between lanes.
  • Blocking Plan Gate: Presents the plan summary and requires an explicit user choice to proceed or stop before execution; headless runs stop after planning.
  • Bounded Fix Cycle: Runs at most one review-fix-review cycle, then reports unresolved findings instead of looping.
  • Use Case: A developer runs "/gitnexus-lfg Add retry support to the ingestion pipeline" and gets a plan, a checkpoint to approve it, verified atomic commits, and a review of the branch diff or open PR.

Quick Start

Ask your AI assistant to run the gitnexus pipeline on your task, for example by invoking /gitnexus-lfg followed by a task description or an existing plan file path.

Frequently Asked Questions about gitnexus-lfg

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the GitNexus plan-work-review pipeline on a task?

Invoke /gitnexus-lfg followed by a task description in Claude Code, or ask Codex CLI to run the gitnexus pipeline. The skill plans the change, pauses at a blocking gate for your approval, executes verified atomic commits, and reviews the result.

Can I skip the planning step with an existing plan file?

Yes, pass a plan file path such as docs/plans/<plan>.md instead of a task description. The pipeline skips the planning lane and starts directly at the gate, where you choose whether to proceed to execution.

Does gitnexus-lfg work in headless or non-interactive runs?

In headless runs the pipeline stops after the planning lane because no one can answer the blocking gate. The plan file becomes the deliverable, and the final report states that execution was not attempted.

When should I use gitnexus-work directly instead of the full pipeline?

For trivial or small-bounded tasks finishable in well under roughly 35 turns, the planning pass costs more than it returns. The skill flags these cases up front and offers gitnexus-work direct mode as an alternative.

Does the pipeline push commits or open pull requests automatically?

No, the pipeline never pushes or opens a PR on its own. The final report lists commits, verification status, and review verdict, then offers pushing and PR creation as explicit next steps for the user.