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.