Skill Claude CodeCodex
Maps engineering ownership risk in a repository using repo evidence such as git history, churn, bus factor, CODEOWNERS coverage, test density, and orphaned or unclear-owner surfaces. Use when a user says map ownership risk, find bus factor hotspots, which files look orphaned, high-change low-test areas, or asks for a…
Skill Claude CodeCodex
Hunts for concrete performance bottlenecks in a scoped repository surface using profiler output, benchmarks, query plans, traces, bundle analysis, or repo evidence, then returns the smallest high-value follow-up experiments or fixes. Use when a user says find performance bottlenecks, why is this slow, profile this…
Skill Claude CodeCodex
Reviews open or draft pull requests for engineering risk before merge, focusing on missing validation, hidden coupling, rollout and rollback gaps, migrations, feature flags, and other agent-safe next actions. Use when a user says review this PR for risk, pre-merge review, is this PR safe to merge, or asks for a…
Skill Claude CodeCodex
Scans recent commits in one or more repositories, identifies likely bugs using concrete repo evidence only, and proposes tightly scoped remediation sessions. Use when a user says scan recent commits for bugs, what did I probably break, review yesterday's changes for regressions, or asks for a commit-scoped bug hunt.…
Skill Claude CodeCodex
Reviews a repository and returns a short, best-first backlog of small, low-risk refactor tickets with clear write boundaries and validation paths. Use when a user says find refactor opportunities, what small cleanup tickets should we hand to agents, give me parallelizable refactors, or asks for narrow maintainability…
Skill Claude CodeCodex
Inspects an unfamiliar software repository and produces a concrete orientation report covering structure, tooling, entry points, boundaries, active surfaces, and safe places to start work. Use when a user says help me understand this repo, map this codebase before I edit it, where should I start, or asks for an…
Skill Claude CodeCodex
Audits a repository, workspace, or monorepo for dependency vulnerabilities, outdated security-sensitive packages, license issues, and dependency hygiene gaps, then compiles one evidence-backed report. Use when a user says run a security audit, check dependencies and licenses, audit this monorepo for vulnerable…
Skill Claude CodeCodex
Identifies and prioritizes the highest-value test coverage gaps in a repository or workspace, then incrementally adds or strengthens tests using the local test stack and cleanly scoped subagent work when available. Use when a user says improve test coverage, find weak tests, add missing test cases, run a recurring…
Plugin Claude Code
8 Claude Code skills that run on a cadence to fight code entropy — method brevity, naming clarity, duplication detection, broken windows. See cdd.dev/skills/hone.
Instructions file CodexOpenCode
AGENTS.md instructions for ckorhonen/hone-skills, covering hone skills & eval suite, repository scope, naming convention, installation and marketing site (site/).
Skill Claude CodeCodex
Finds manual processes that could be automated: manual deploy steps in READMEs, setup instructions that could be scripts, repetitive git workflows, manual testing procedures, and undocumented tribal knowledge. Also checks for artifacts not in source control. Use monthly to surface automation ROI. Do NOT use for code…
Skill Claude CodeCodex
Detects entropy signals in a codebase: stale TODOs, disabled tests, lint suppressions, commented-out code, dead imports, empty catch blocks, and deprecated API usage. Designed for daily runs to catch quality erosion early. Do NOT use for feature work, refactoring planning, or security audits.
Skill Claude CodeCodex
Finds duplicated code patterns across the codebase including exact copies and structural duplication (same logic with different variable names). Ranks by frequency and suggests extraction candidates. Designed for weekly runs. Do NOT use for method length, naming, or style concerns.
Skill Claude CodeCodex
Finds code that obscures its intent: unclear variable names, nested ternaries, boolean parameters without names, overly clever one-liners, and comments that restate code instead of explaining why. Focuses on recently changed files. Do NOT use for method length, duplication, or test naming concerns.
Skill Claude CodeCodex
Surfaces magic numbers, unexplained string literals, hardcoded URLs, configuration values buried in code, and other "magical" values that should be named constants or config entries. Use when you want a weekly sweep for unnamed literals. Do NOT use for style or formatting audits.
Skill Claude CodeCodex
Scans a codebase for methods and functions that exceed configurable length thresholds. Reports a ranked list of the longest methods with file:line, language, and surrounding complexity signals. Designed for scheduled weekly runs. Do NOT use for style formatting, indentation, or naming concerns.
Skill Claude CodeCodex
Flags classes, modules, and functions with vague generic names like Manager, Handler, Processor, Helper, Utils, Service, Base, Common, and Misc. Suggests more specific alternatives based on what the code actually does. Use weekly to prevent naming drift. Do NOT use for variable-level naming or style enforcement.
Skill Claude CodeCodex
Checks that test method and function names read as complete sentences describing behavior. Flags cryptic names like test1, testFoo, or abbreviated names that do not describe what is being tested. Designed to run on every PR. Do NOT use for test coverage, test structure, or non-test code.