Skill Claude CodeCodex
Use when a test fails, a runtime error occurs, or a behavioral regression is reported — reproduce first, then fix the root cause within scope.
Skill Claude CodeCodex
Use when a test fails, a runtime error occurs, or a behavioral regression is reported — reproduce first, then fix the root cause within scope.
Skill Claude CodeCodex
Use when a change stays within 1-3 files and does not need a formal spec (bug fixes, validation tweaks, small config changes) — self-escalates to implement if scope grows.
Skill Claude CodeCodex
Use when you struggle with the same sub-problem 2+ times then find a working approach — captures the failed attempts and the fix as a reusable lesson, no engineer correction required.
Skill Claude CodeCodex
Use when context nears limits, before ending a long session with in-progress work, or handing off to a teammate — captures session state into a recovery artifact so a new session resumes cleanly.
Skill Claude CodeCodex
Full feature implementation loop orchestrating planning, batching, verification, and review skills.
Skill Claude CodeCodex
Use when executing an approved multi-file implementation to ensure each batch compiles, tests, and stays within the approved manifest.
Skill Claude CodeCodex
Mine past session transcripts for durable lesson and memory candidates, applying a reject-by-default rubric — suggest-only, never auto-writes.
Skill Claude CodeCodex
Audit the lessons stores for staleness — verify cited paths/symbols, triage each lesson Keep/Update/Consolidate/Retire — suggest-only, retirement is always a human decision.
Skill Claude CodeCodex
Run an MTK install health check (core files, components, hooks, integrity, environment fit) with PASS/WARN/FAIL diagnostics, --json for CI, and --fix for safe auto-repairs.
Skill Claude CodeCodex
One-stop setup entry point that bootstraps a repo or re-runs architecture audit.
Skill Claude CodeCodex
Unified entry point that routes natural language requests to the right MTK skill.
Skill Claude CodeCodex
Use after a spec is approved and before multi-file implementation begins, to break work into verifiable batches with checkpoints.
Skill Claude CodeCodex
Mine recurring reviewer-feedback phrases from the last N merged PRs and surface them as suggest-only [MINED:feedback] candidates.
Skill Claude CodeCodex
Fast security-focused review of staged changes before every commit, checking only critical compliance rules.
Skill Claude CodeCodex
Use before approving a spec or starting a multi-file implementation to confirm no existing skill, helper, handler, or lesson already covers the proposed work.
Skill Claude CodeCodex
Promote a personal lesson from .claude/lessons/personal.md or Claude Code native memory to the team-wide tasks/lessons.md, rewording for team applicability.
Skill Claude CodeCodex
Periodic AI-readiness report — scorecard against 12 named assets plus PR review mining from the last N merged PRs.
Skill Claude CodeCodex
Use when a decision needs current external/web info (library best-practices, version behavior, migration guidance) rather than local sources — runs grounded web research and returns a cited brief.
Skill Claude CodeCodex
Use when the change touches auth, secrets, audited state, audit trails, infrastructure, or external inputs — treat security as a design constraint, not final polish.
Skill Claude CodeCodex
Audit the repo to extract architecture principles, or with --merge unify audits from multiple repos into a single team-wide document.
Skill Claude CodeCodex
One-time repo setup that detects tech stack, audits the codebase, pulls coding guidelines, and generates a project-specific CLAUDE.md.
Skill Claude CodeCodex
Judges the codebase against the agreed architecture-principles.md/conventions.md and reports drift as graded, read-only work items — never auto-fixes.
Skill Claude CodeCodex
Refresh generated setup artifacts (principles, conventions, detected tools, AGENTS.md, configs, indexes) against codebase drift — proposes diffs for engineer-edited files instead of overwriting.
Skill Claude CodeCodex
Use when framework, SDK, or library behavior is unfamiliar or version-sensitive — verify from local authoritative sources (decompiled/SDK code, in-repo docs) before implementing.