Coding standards, frameworks, refactoring, and code review (18.6K skills)
Start a structured OpenSpec change for a feature, fix, or modification. The skill creates a named change scaffold, reports its workflow and status, and shows instructions for the first planning artifact so the user can decide what to draft next.
Implement an OpenSpec change by grouping tasks into dependency-ordered waves, running parallel work within each wave, verifying scenarios, and reviewing the resulting diff. It leaves commits and archiving for the user.
Continue an OpenSpec change by checking its current artifact status and creating the next artifact in the workflow. It helps move planning forward one step at a time, following the change’s schema and dependencies.
Merge an OpenSpec change’s delta specifications into the project’s main specs while preserving requirements and scenarios that the change does not address. Use it to update specifications independently, leaving the change active for further work or later archiving.
Learn an OpenSpec change cycle through guided work on a real codebase. The skill helps select a small task, create planning artifacts, implement the work, and archive the change while explaining each stage as it happens.
Plan one OpenSpec change through a coverage interview, codebase research, and evidence-based challenge of key decisions. Agent roles draft and critique the artifacts, followed by mechanical CLI validation, so the user can review a complete plan before implementation.
Use this skill to document a project's existing capabilities as OpenSpec baseline specs. It researches the code, confirms a capability map with the user, drafts and critiques specifications, then validates them with the OpenSpec CLI.
Revise an existing OpenSpec change plan by incorporating new decisions and checking its planning artifacts for contradictions or gaps. It works with artifacts already in place and keeps implementation code untouched.
Create a complete set of OpenSpec planning artifacts from a change description: a proposal, specification delta, design, and implementation tasks. The workflow prepares the change for review and later implementation; it does not modify project code.
Generate the OpenSpec artifacts required to begin implementation in one workflow. The skill checks dependencies, reads project context and existing code, then creates the required planning files in order so the change is ready for implementation.
Batch archive selected OpenSpec changes after reviewing their artifacts, task progress, and spec conflicts. It checks implementation evidence to decide which conflicting deltas to sync, then reports archived, skipped, and failed changes.
Finalize an implemented OpenSpec change by checking its artifacts and task status, reviewing whether delta specs need syncing, and moving the change into the archive. It reports incomplete work and requires confirmation before proceeding with warnings.
Use this skill to implement tasks tracked in an OpenSpec change. It checks the project and change status, reads the required context files, makes scoped code updates, and records completed tasks while surfacing ambiguity or blockers.
Use this skill to install the seven oh-my-openspec role agent files for Codex, approve its OpenSpec MCP server, and verify setup. It checks existing files and avoids replacing differing files unless explicitly forced.
Use this skill to review a finished oh-my-openspec session for problems in its prompts. It compiles raw evidence from commands, agent reports, friction, and the final diff, then presents cited findings without changing files.
Route one OpenSpec change to the single-change archive workflow, or multiple changes to the bulk workflow. It requires specification deltas to be synced before archiving, validates before and after, and stops if syncing is blocked or validation fails.
Explore an idea or project problem before or during an OpenSpec change. The skill investigates relevant code and artifacts, compares options, surfaces risks, and helps clarify requirements; implementation stays outside this mode.
Split a large code change into smaller pull requests, keep review fixes in the slice that owns the code, and carry them through dependent branches. It also guides the ordered merge and cleanup of the stack.
Turn bug reports, feature requests, external pull requests, alerts, and feedback into evidence-based recommendations. The skill checks reported behavior and prior decisions, identifies unknowns or duplicates, and creates a standalone brief for accepted or likely accepted work so another agent can continue it.
Review a CLI, API, MCP tool, SDK, or proposed interface from an AI agent's perspective. Examine discovery, first use, output, and error recovery, then report reproducible findings with their impact and smallest suggested fix.
Finds structural friction that makes code changes costly, then compares module or boundary designs by their effect on real call sites. It returns ranked proposals with test changes, migration steps, and reversal risks, without editing code.
Review a branch against a project’s `.archcore/` records by checking code against documentation and documentation against code. Get evidence-backed findings that distinguish stale specifications from code that violates current rules, plus project health, drift, audit, or feature closeout reports when requested.
Choose Claude Code skills and rules to install at user or project level. The workflow checks installed files and path references, reports problems, and can tailor the installed materials to a project's tech stack and preferences.
Record significant architecture choices as concise ADR documents alongside the code. Capture the context, alternatives, rationale, and consequences so developers can understand why a framework, database, API, or other design direction was chosen.