regression-issue-fix

Enforces intake validation and fixture-first workflow for fixing Phase 1 extractor regression issues.

26|8|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/vibeic/vibe-ic --skill regression-issue-fix-vibeic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regression-issue-fix
Source: https://github.com/vibeic/vibe-ic/tree/main/vibe-ic-marketplace/plugins/vibe-ic/skills/regression-issue-fix
Command: npx skills add https://github.com/vibeic/vibe-ic --skill regression-issue-fix-vibeic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Regression issues for Phase 1 picker/extractor components often arrive without verbatim input snippets, expected outputs, or reproducible fixtures, causing repeated guessing rounds and thrashing across multiple plugin releases. This Skill gates every fix behind a mandatory intake check so incomplete issues are bounced back before any code is touched. ## Core Features & Use Cases - Hard intake gate: Runs regression_issue_intake_check.py before any code is read, refusing to start fixes on issues missing verbatim input, expected output, or a drop-in fixture. - Fixture-first fixing: Requires the new fixture to fail on current code before writing the fix, then runs the full fixture suite with a pre-commit thrash guard against silent fixture flips. - Self-verify and close lifecycle: Guides the agent to reproduce the original failure, run the full CI suite, push a chip-agnostic fix, and close the issue with the core-closed label and a structured 5-section comment. - Use Case: When asked to "fix issue #42" affecting the L6.fsm_states extractor, the Skill first validates the issue's completeness, lands the fixture, confirms it fails, then drives the fix through verification and closure. ## Quick Start Ask the agent to read and fix GitHub issue number N for a Phase 1 picker or extractor regression, and it will run the intake check before doing anything else.

Frequently Asked Questions about regression-issue-fix

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

FAQPage Schema
How do I fix a Phase 1 extractor regression issue in vibe-ic?▼

Run the intake check program with the issue number first. If it passes and emits a fixture, confirm the fixture fails on current code, write the fix in the picker or L-doc generator, run the full fixture suite, then self-verify and close the issue with the core-closed label.

What happens when a regression issue is missing the input snippet?▼

The intake check exits with code 1 and names every missing field. The workflow stops and posts a comment asking the verifier to fill the gaps using the picker-or-extractor-regression issue template, with no guessing rounds allowed.

Why must the new fixture fail before writing the fix?▼

A failing fixture proves the regression reproduces on current code. If the test passes immediately, the issue is stale or already fixed, so the agent comments and stops instead of pushing a no-op release.

What is the core-closed label in the issue lifecycle?▼

Core-closed marks an issue the core agent self-verified and closed. The field agent audits closed core-closed issues against the real benchmark, adding field-verified on success or reopening with counter-evidence if the fix is inadequate.

Can I commit a fix that flips an existing fixture result?▼

Only with explicit acknowledgment. The pre-commit thrash guard refuses fixture flips unless the commit message carries a fixture-flip-acknowledged line naming the project and the old-to-new behavior change.