skills.rest
micfre
micfreCOMMUNITY
Explore all skills by this author →
GitHub

bmild-qa

Diagnose CI failures and verify development Slices against acceptance criteria.

3|Updated Mar 26, 2026
Search Tags:#qa#verification#quality-gates#root-cause-analysis#bug-fixing#spec-driven-development#test-automation
One-click install
npx skills add https://github.com/micfre/BMILD --skill bmild-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmild-qa
Source: https://github.com/micfre/BMILD/tree/main/.agents/skills/bmild-qa
Command: npx skills add https://github.com/micfre/BMILD --skill bmild-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill eliminates guesswork and unreproduced fixes in BMILD spec-driven development workflows by enforcing evidence-based defect resolution, ensuring code meets requirements before release, and preventing regression debt from unverified changes.

Core Features & Use Cases

  • Root Cause Analysis (RCA): Systematically diagnose bugs, test failures, and CI errors with structured hypothesis testing and evidence collection.
  • Slice Verification: Validate completed development Slices against acceptance criteria and quality gates, ensuring all requirements are met.
  • Verification Matrix Management: Create, repair, and maintain test matrices that map requirements to demonstrable proof, eliminating gaps in test coverage.
  • Minimal Bug Fixes: Apply scoped, evidence-based fixes only after root cause confirmation, with mandatory regression tests to prevent recurrence.
  • Use Case: When a CI pipeline fails after a new feature is merged, use this skill to reproduce the failure, identify the root cause, apply a minimal fix, and add a regression test to catch the issue in the future.

Quick Start

Use the bmild-qa skill to diagnose the failing user authentication test in the latest CI run, confirm the root cause, and provide a minimal fix plan with a regression test requirement.

Frequently Asked Questions about bmild-qa

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

FAQPage Schema
How do I perform root cause analysis on unreproduced bugs in a CI pipeline?▼

Root cause analysis for unreproduced bugs applies structured hypothesis testing and evidence collection to systematically diagnose CI failures. This approach confirms the defect origin before applying any code changes, preventing guesswork and ensuring fixes target the actual issue.

How do I verify completed development Slices against acceptance criteria?▼

Verifying completed development Slices involves validating the implemented code against predefined acceptance criteria and quality gates. This ensures all requirements are demonstrably met and prevents regression debt from unverified changes before code promotion to production.

What is a verification test matrix and when do I need to repair one?▼

A verification test matrix maps requirements to demonstrable proof, eliminating gaps in test coverage. You need to repair or create one when missing quality gates allow unverified changes, ensuring regression tests provide proof and validate quality gates before production release.

What's the best way to fix failing tests without introducing regression debt?▼

Fixing failing tests without regression debt requires applying scoped, evidence-based fixes only after root cause confirmation. This method mandates adding regression tests to catch future recurrences, ensuring minimal bug fixes align with spec-driven development workflows.

Does evidence-based defect resolution work for spec-driven development workflows?▼

Evidence-based defect resolution is designed specifically for spec-driven development workflows. It enforces quality gate validation and verification of completed Slices, ensuring code meets requirements before release and preventing unreproduced fixes from entering production.

Why should I use structured hypothesis testing for CI failure diagnosis?▼

Structured hypothesis testing for CI failure diagnosis eliminates guesswork by requiring evidence collection before applying fixes. It ensures minimal, scoped bug fixes are applied only after root cause confirmation, with mandatory regression tests preventing future recurrence.

Related Skills

Explore More Software Engineering Skills→
micfremicfre
3

bmild-dev

Implement planned BMILD Slices, fix bugs, and build prototypes.

Community
Advanced
proffesor-for-testingproffesor-for-testing
436

regression-testing

Automate regression test selection and analysis across CI/CD pipelines.

Community
Intermediate
cslsoftwarescslsoftwares

developer-delphi-testing-and-quality

Define and enforce Delphi/FPC testing and quality gates across CI pipelines.

Community
Advanced
withzombieswithzombies
80

fixing-bugs

Automate bug fixing from issue creation through regression testing and closure.

Community
Advanced