lens-core-bugfix

Runs a governed Lens core bugfix through isolated branch, validation, and PR workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Handling Lens core bug reports without a controlled process leads to unvalidated fixes, tangled branches, and missing pull request handoffs. This Skill enforces a governed workflow so each bounded bugfix moves through an isolated feature branch, focused validation, and a clean PR handoff. ## Core Features & Use Cases - Isolated Branch Workflow: Creates a dedicated feature branch for each Lens core bugfix to keep changes separated from mainline work. - Focused Validation: Runs targeted validation on the fix before it proceeds to review. - PR Handoff: Packages the validated fix into a pull request for review and merge. - Use Case: A maintainer receives a bounded Lens core bug report and invokes this command to branch, implement, validate, and open a PR without manual orchestration. ## Quick Start Ask the assistant to run the lens-core-bugfix command on a specific bounded Lens core bug report to produce a validated fix on an isolated branch with a pull request.

Frequently Asked Questions about lens-core-bugfix

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

FAQPage Schema
How do I run a governed bugfix workflow for a Lens core bug?

Invoke the lens-core-bugfix command with a bounded Lens core bug report. The workflow creates an isolated feature branch, implements the fix, runs focused validation, and hands off the result as a pull request.

What kinds of bugs should I fix with an isolated branch workflow?

Use it for bounded Lens core bug reports that need a dedicated feature branch, focused validation, and a PR handoff. Large refactors or multi-module changes fall outside its intended scope.

Does lens-core-bugfix require the Lens runtime to be installed?

Yes. The skill delegates implementation to the installed Lens runtime so module validation can confirm the help entry and prompt registration are not orphaned in source.

When should I not use a governed single-bugfix workflow?

Avoid it for unbounded or exploratory fixes, cross-cutting refactors, and changes spanning multiple modules. Those cases need broader planning rather than a single isolated branch and validation pass.