Documentos

Creates slash commands from procedural doc sections. Use when transforming documentation prose into executable commands.

Use when accepted findings require bounded repair changes and a structured repair summary.

Use when installing or verifying this marketplace in Claude and Codex, aligning selected plugins, MCP settings, and Codex execution defaults.

Audits whether one implemented architectural pattern fits project needs and best practices. Use when checking pattern fitness.

Finds code that can be safely deleted: unreachable, unused, obsolete compatibility, and commented-out code. Use when pruning dead code.

Checks diagnosability through structured logs, metrics, traces, correlation IDs, and useful log levels. Use when auditing incident visibility.

Configures global exception handling middleware. Use when adding centralized error handling to .NET or Python backends.

Checks redundant fetches, N+1 loops, over-fetching, missing bulk operations, wrong caching scope. Use when auditing query efficiency.

Upgrades .NET NuGet packages with breaking change handling. Use when updating .NET dependencies.

Reviews skills (D1-D11 + M1-M6 criteria) or .claude/commands for quality. Use when validating skill correctness before release.

Generates seed data from ORM schemas or entity definitions to any target format. Use when populating databases for development.

Builds and launches Docker containers with health verification. Use when validating that containerized services start correctly.