consistency-closure

Detect divergent code implementations and migrate them to an approved canonical form.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/skylarsabo/code-ops --skill consistency-closure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consistency-closure
Source: https://github.com/skylarsabo/code-ops/tree/main/plugins/rigor/skills/consistency-closure
Command: npx skills add https://github.com/skylarsabo/code-ops --skill consistency-closure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps maintain code consistency by identifying and correcting divergent implementations of the same concept, enforcing a single, canonical form.

Core Features & Use Cases

  • Concept Space Selection: Choose the area of code you want to normalize (e.g., error handling, data access).
  • Variant Inventory: Automatically detect different implementations of the chosen concept.
  • Canonical Form Selection: Decide on the best implementation and rationale.
  • Migration and Enforcement: Migrate all other implementations to the canonical form and enforce it with mechanical checks.
  • Use Case: If you have multiple implementations of error handling in your codebase, this Skill can ensure all are consistent and follow a single, standardized approach.

Quick Start

Invoke the consistency-closure skill by running: /rigor:consistency-closure --concept space "error handling"

Frequently Asked Questions about consistency-closure

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

FAQPage Schema
How do I enforce code consistency for divergent implementations in my codebase?

Code consistency is enforced by identifying divergent implementations of a concept, selecting a canonical form, migrating all variants to match it, and applying linting rules for mechanical enforcement.

What is canonical form selection and how does it normalize a codebase?

Canonical form selection is the process of choosing a single, standardized implementation for a specific concept space, which normalizes a codebase by migrating all divergent variants to match the agreed-upon standard.

Can I use linting to maintain codebase maintenance after normalizing error handling?

Linting can be used to maintain codebase maintenance by enforcing the selected canonical form, providing mechanical checks that prevent future divergent implementations of the normalized concept.

What's the best way to resolve multiple error handling patterns during codebase maintenance?

The best way to resolve multiple error handling patterns is to inventory the variants, interactively approve a single canonical implementation, and migrate all other code to match that standard.

Does code normalization require manual approval before modifying existing implementations?

Code normalization requires user interaction for canonical form approval, ensuring you explicitly decide on the best implementation and rationale before any code modification takes place.