bmad-lens-core-bugfix

Orchestrates Lens core bug fixes through branch creation, implementation delegation, and PR automation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fixing bugs in the Lens core codebase requires coordinating bug intake records, fresh git branches, implementation, validation, commits, pushes, and pull requests across multiple repositories. This Skill automates that entire flow so a single bug report becomes a merged-ready PR without manual git handoffs. ## Core Features & Use Cases - Bug Intake Recording: Creates a governance bug artifact from title, description, repro steps, expected, and actual behavior before any code changes. - Fresh Branch Enforcement: Derives a unique feature/lens-core-bugfix-{slug} branch from the develop base branch for every distinct bug, blocking accidental branch reuse. - Delegated Implementation with Completion Gate: Delegates the fix to the quick-dev workflow, then automatically commits, pushes, creates the PR, and closes the bug artifact without user confirmation. - Use Case: A user reports that a Lens command produces wrong output. They provide the repro steps, and the Skill records the bug, fixes it in the target repo, opens a PR against develop, and archives the bug under bugs/Fixed/. ## Quick Start Run /lens-core-bugfix and provide the bug title, description, reproduction steps, expected behavior, and actual behavior to get a fix branch and pull request automatically.

Frequently Asked Questions about bmad-lens-core-bugfix

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

FAQPage Schema
How do I fix a Lens core bug with an automated PR workflow?

Invoke /lens-core-bugfix with the bug title, description, repro steps, expected behavior, and actual behavior. The flow records a bug artifact, creates a fresh feature branch from develop, implements the fix via quick-dev, then commits, pushes, and opens the PR automatically.

What inputs are required to run the Lens core bugfix flow?

Five fields are mandatory: title, description, repro_steps, expected, and actual. If any field is missing, the flow asks only for the missing fields and stops until the report is complete.

Does the bugfix flow reuse an existing branch or pull request?

No. Every distinct bug gets its own branch derived from the bug slug, which includes a content hash. Reusing a branch for a newly created bug artifact triggers a branch_reuse_blocked stop unless the branch exactly matches the same bug slug.

What happens if the bugfix produces no code changes?

The flow stops with a structured bugfix_no_changes blocker instead of reporting success. A valid run requires a non-empty working branch, commit hash, PR URL, and a bug artifact path under bugs/Fixed/.

Can the bugfix flow use a git worktree when the target repo is dirty?

No. The flow explicitly forbids creating or switching to git worktrees. A dirty target repository or a failed prepare-dev-branch step is a hard blocker until the user explicitly approves continuing in the canonical target path.