lens-nextlens-bugfix

Orchestrates governed NextLens bugfixes from bug recording through branch preparation, delegation, and PR closeout.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-nextlens-bugfix-crisweber2600
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lens-nextlens-bugfix
Source: https://github.com/crisweber2600/Lens.Core.Src/tree/main/_bmad/lens-work/skills/lens-nextlens-bugfix
Command: npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-nextlens-bugfix-crisweber2600

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fixing bugs in the NextLens runtime requires coordinating many governed steps—recording the bug, creating a fresh branch, delegating bounded implementation, pushing, opening a PR, and closing the bug artifact—and doing any of them manually risks bypassing governance gates or writing outside the allowed target root. ## Core Features & Use Cases - Namespaced bug recording: Generates a fix spec via nextlens_fix_spec.py and creates a namespaced bug artifact under bugs/nextlens/ before any code changes. - Governed branch and delegation flow: Prepares a fresh feature/nextlens-bugfix-{slug} branch through git orchestration, then delegates implementation strictly inside TargetProjects/nextlens/src/NextLens. - Conductor-owned completion gate: Verifies commits, changed-file boundaries, push, PR creation, Doctor validation evidence, and bug closeout before reporting success. - Use Case: A user reports that a NextLens runtime command misbehaves; the skill records the bug, creates a dedicated branch, delegates the bounded fix, opens the PR, and closes the bug artifact with Doctor evidence. ## Quick Start Ask the assistant to run the NextLens bugfix flow by describing what happened, what should have happened, and providing the relevant chat history.

Frequently Asked Questions about lens-nextlens-bugfix

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

FAQPage Schema
How do I fix a NextLens runtime bug with governance gates?

Provide what happened, what should have happened, and the chat history. The skill records a namespaced bug, prepares a fresh feature branch, delegates the bounded implementation, and completes push, PR creation, and bug closeout through governed commands.

What inputs are required to start a NextLens bugfix?

Three inputs are required: what_happened, what_should_have_happened, and chat_history. Optional metadata includes severity, salmon_signal_id, evidence_refs, suspected_target_surface, validation_request, and operator_notes.

When should I use lens-core-bugfix instead of the NextLens bugfix flow?

Use lens-core-bugfix when the fix requires changes in the Lens core source repo or another non-NextLens repository. The NextLens bugfix flow only handles changes inside the NextLens source tree, including new NextLens skills and install-surface updates.

Why does the NextLens bugfix stop with branch_reuse_blocked or bugfix_no_changes?

branch_reuse_blocked occurs when a prepared branch is reused for a different bug, since each bug requires its own fresh branch. bugfix_no_changes occurs when HEAD is unchanged after delegation, because no-op completions are forbidden.

Can the implementation delegate push code or create the PR?

No. The delegate only makes bounded edits and one conventional commit inside the allowed write root. The conductor owns push, PR creation, PR recording, Doctor evidence capture, and bug closeout.