code-quality

Enforce user-approved plans before applying atomic code changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/vendeesign/codebloom --skill code-quality-vendeesign
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/vendeesign/codebloom/tree/main/skills/code-quality
Command: npx skills add https://github.com/vendeesign/codebloom --skill code-quality-vendeesign

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents unintended code changes by enforcing a validated plan before any write or modification, ensuring guardrails are active in software projects.

Core Features & Use Cases

  • STOP rules that block coding until the user confirms the plan.
  • Atomic, per-file changes with surgical modifications and clear rollback guidance.
  • Guidance to maintain consistency with design standards and automatic documentation reminders.

Quick Start

Provide a plan first and obtain explicit user validation before applying any code changes.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I enforce a code review plan before modifying files?

To enforce a code review plan before modifying files, you must present an explicit plan and obtain user validation. This process blocks coding until the plan is confirmed, ensuring guardrails are active.

What are atomic changes in software engineering workflows?

Atomic changes are surgical, per-file modifications that include clear rollback guidance. This approach ensures consistency with design standards and prevents unintended code changes during refactoring or feature additions.

How do I prevent unintended code changes during refactoring?

To prevent unintended code changes during refactoring, enforce a validated plan before any write or modification. STOP rules block coding until the user confirms the plan and guardrails are active.

Do I need to validate my development process for every coding task?

You need to validate your development process for every coding, refactoring, or feature addition task. This ensures explicit plan presentation and user approval prior to implementation, maintaining software quality.

What is the best way to maintain documentation consistency when adding features?

The best way to maintain documentation consistency when adding features is using guardrail-driven documentation reminders. These reminders automatically prompt you to update docs alongside atomic, per-file code modifications.

Can I apply code quality guardrails across any software project?

You can apply code quality guardrails across any software project. They enforce explicit plan presentation, user approval prior to implementation, and atomic per-file changes regardless of the specific project.