bmm

Orchestrate small repository edits with file-limit and quality-gate validation.

1|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/jongensutrecht/demo-ai-stack --skill bmm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmm
Source: https://github.com/jongensutrecht/demo-ai-stack/tree/main/lars%20skills/bmm
Command: npx skills add https://github.com/jongensutrecht/demo-ai-stack --skill bmm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you make small repository changes quickly without losing quality, keeping the work tightly scoped, testable, and evidence-driven.

Core Features & Use Cases

  • Micro-change workflow: Handles small bug fixes, UI tweaks, copy edits, config updates, and compact refactors.
  • Hard quality guards: Enforces file limits, real runtime proof, specs, fixed ports, and quality-gate checks.
  • Practical use cases: Use it when you need to change one feature, verify it on a running app, and avoid planning overhead or broad refactors.

Quick Start

Ask the Skill to make your small change, then follow its micro-brief, test, spec, and quality-gate workflow end to end.

Frequently Asked Questions about bmm

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

FAQPage Schema
How do I enforce quality gates for small code changes without adding planning overhead?

Quality gates for small code changes are enforced by applying strict file-limit checks, requiring real runtime evidence, and validating spec updates before a micro-change is approved. This keeps tightly scoped bug fixes and UI tweaks testable without broad refactoring.

What is the best way to manage a micro-change workflow for local repository edits?

A micro-change workflow orchestrates local repository edits by enforcing fixed-port discipline and quality-gate validation. It requires real runtime proof and spec updates, ensuring small config updates or bug fixes stay scoped, testable, and evidence-driven.

Can I use this micro-change approach for compact refactors and UI tweaks?

Yes, this micro-change approach handles compact refactors, UI tweaks, copy edits, and config updates. It applies file-limit checks and fixed-port discipline to verify changes on a running app, ensuring the work remains small and evidence-driven.

How do I verify runtime evidence for a bug fix in a running app?

Runtime evidence for a bug fix is verified by testing the change on a running app using fixed ports. The workflow requires real runtime proof and quality-gate validation, ensuring the small repository change functions correctly before completion.

When should I avoid using a micro-change workflow for repository updates?

You should avoid a micro-change workflow when your task requires broad refactoring, exceeds file-limit checks, or involves planning overhead. This approach is designed for small, scoped local repository edits like UI tweaks and config updates that stay tightly contained.

Do I need to update specs when making small bug fixes in a repository?

Yes, spec updates are required when making small bug fixes. The micro-change workflow enforces spec updates alongside real runtime evidence and quality-gate validation, ensuring every local repository edit remains documented and evidence-driven.