skills.rest
openchamber
openchamberOFFICIAL
Explore all skills by this author →
GitHub

openchamber-change-discipline

Guides risk-classified code changes with scoped validation across OpenChamber workspaces.

9.5k|1.0k|Updated Sep 11, 2025
Search Tags:#Refactoring#Validation#Testing#Monorepo#typeScript#code discipline#risk classification
One-click install
npx skills add https://github.com/openchamber/openchamber --skill openchamber-change-discipline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openchamber-change-discipline
Source: https://github.com/openchamber/openchamber/tree/main/.agents/skills/openchamber-change-discipline
Command: npx skills add https://github.com/openchamber/openchamber --skill openchamber-change-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modifying a multi-workspace codebase like OpenChamber risks breaking shared contracts, persisted data, and platform runtimes when changes are under-validated or over-engineered. This Skill enforces a disciplined process that matches validation effort to actual change risk.

Core Features & Use Cases

  • Risk Classification: Categorizes every change as local implementation, module contract, cross-workspace contract, persisted/external behavior, or platform/runtime behavior, each with defined planning consequences.
  • Validation Matrix: Maps each change type to its minimum required validation, from focused package tests to workspace-wide type-checks, dead-code analysis, and compatibility round-trip tests.
  • Structural Discipline: Enforces minimal complete diffs, explicit dependencies, early failure rejection, and explicit rollback/cleanup for destructive or multi-step operations.
  • Use Case: When renaming an exported type shared between the web and VS Code packages, the Skill directs you to trace all consumers, run workspace-wide type-checks plus bun run dead-code, and update owning docs.

Quick Start

Ask the agent to implement a fix or refactor in the OpenChamber repository and it will classify the change risk, scope the diff, and run the matching validation before completing.

Frequently Asked Questions about openchamber-change-discipline

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

FAQPage Schema
How do I safely modify shared code across OpenChamber workspaces?▼

Classify the change as a cross-workspace contract, trace every actual consumer and runtime, then run workspace-wide type-check and lint plus affected builds and tests. Choose validation by tracing real consumers rather than running everything reflexively.

What validation is required when changing an exported type or entrypoint?▼

Changes that add, delete, or rename source files, exports, types, entrypoints, or import shapes require running `bun run dead-code` in addition to relevant package checks. Type-only shared contracts need compile-time consumer validation.

When does a change require a data migration in OpenChamber?▼

Require a migration only when existing stored data needs conversion. Test downgrade compatibility only when older application versions are concrete supported consumers, and define rollback as restoring valid state after a failed write or migration.

How should tests be designed for behavior-preserving refactors?▼

Establish the current behavior before changing structure, and prefer testing observable contracts, state transitions, and failure handling. Keep refactor tests resilient to equivalent internal implementations rather than asserting internal call order.

When should I avoid adding abstractions or compatibility layers?▼

Add retries, caches, compatibility paths, or lifecycle machinery only with concrete evidence of need. New abstractions must pay for a real boundary, invariant, or stable repetition rather than speculative reuse.

Related Skills

Explore More Software Engineering Skills→
0xdeafcafe0xdeafcafe

backfill-feature

Backfill retroactive ADRs, Gherkin specs, and characterization tests for existing software features.

Community
Advanced
WanxiaJaneYangWanxiaJaneYang

repo-standards

Validate code formatting, linting, type-checking, and tests for pull requests.

Community
Basic
materkeymaterkey
1

review-feature-architecture

Review feature-level architecture in plan files or implementation diffs for design risks.

Community
Advanced
nadicodeainadicodeai

test-driven-development

Enforce test-first discipline by requiring a failing test before production code.

Official
Intermediate