Skill Claude CodeCodex
Part of ken-swe
Structured bug fixing with reproduction, root cause analysis, fix design, regression risk analysis, and quality review. Only invoke this skill when the user explicitly asks to use it by name (e.g. "use bug-fix", "run bug-fix") or clearly requests a structured/systematic bug fixing process. Do not invoke for general…
Skill Claude CodeCodex
Part of ken-swe
Review multiple pull/merge requests across GitHub, GitLab, and Azure DevOps in parallel. Thin orchestrator over the single-PR code-review skill — one agent per PR, consolidated summary, optional PR comments. Use when the user wants to review several PRs/MRs at once (release sweep, multi-repo audit, batch review).
Skill Claude CodeCodex
Part of ken-swe
Review changed code for bugs, simplicity, security, and convention adherence using parallel reviewer agents. Use when the user asks to review code, review a PR, check quality, or wants a second pair of eyes before merging.
Skill Claude CodeCodex
Part of ken-swe
Build and maintain a persistent structural index of a Java, Go, Python, or Rust codebase under .codemap/ (graph.json + MAP.md), so other skills explore via the map instead of grep + read loops. Tree-sitter based; supports polyglot repos. Use when starting work in an unfamiliar non-TS/JS repo, when the user asks to…
Skill Claude CodeCodex
Part of ken-swe
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Skill Claude CodeCodex
Part of ken-swe
Autonomous feature development with goal-loop verification. Front-loads all decisions through interactive stages, then drives implementation unattended against verifiable goals — re-architecting, diagnosing, and self-correcting until green or escalation thresholds hit. Use for substantial feature work with a…
Skill Claude CodeCodex
Part of ken-swe
Right-sized guided feature development with three presets (Quick / Standard / Deep) covering everything from one-line tweaks to risky new modules. Invoke for any non-trivial feature work.
Skill Claude CodeCodex
Part of ken-swe
Optimized guided feature development with deep requirement drilling, codebase understanding, and design-quality frontend implementation. Use this skill whenever the user wants to build or implement a feature — whether they say "let's build X", "add feature Y", "implement Z", "I want to create", "can we add", or any…
Skill Claude CodeCodex
Part of ken-swe
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Skill Claude CodeCodex
Part of ken-swe
Interview the user to extract coding standards and project context, grounded in what the codebase already does. Use when user wants to generate a CLAUDE.md, CODINGSTANDARDS.md, or otherwise capture conventions from an existing codebase.
Skill Claude CodeCodex
Part of ken-swe
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Skill Claude CodeCodex
Part of ken-swe
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Skill Claude CodeCodex
Part of ken-swe
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Skill Claude CodeCodex
Part of ken-swe
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
Skill Claude CodeCodex
Part of ken-swe
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
Skill Claude CodeCodex
Part of ken-swe
Turn an ADO user story — or a rough idea — into a verifiable, code-grounded blueprint a TDD executor can build from. Use when the user wants work planned before coding.
Skill Claude CodeCodex
Part of ken-swe
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Skill Claude CodeCodex
Part of ken-swe
Build and maintain a persistent structural index of a TypeScript/JavaScript codebase under .codemap/ (graph.json + MAP.md), so other skills explore via the map instead of grep + read loops. Uses ts-morph for high-fidelity TS/JS parsing (tsconfig path aliases, re-export flattening, JSX). Use when the user asks to…
Skill Claude CodeCodex
Part of ken-swe
Create a PRD with an embedded Design Direction section through user interview, codebase exploration, and design intent capture. Use when building or revamping any feature with frontend or UI work — landing pages, components, UI redesigns — where design intent needs to be locked in before implementation. Extends the…
Skill Claude CodeCodex
Drain ready-for-agent GitHub tickets via do-work subagents — parallel or sequential, one PR or PR-per-ticket.
Skill Claude CodeCodex
Compact the current conversation into a handoff document for another agent to pick up.
Skill Claude CodeCodex
Deliver one tracker work package labeled ready-for-seo-agent through acceptance → delivery → evidence.
Skill Claude CodeCodex
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking,"…
Skill Claude CodeCodex
Research and maintain an evidence-backed SEO/GEO thesis, opportunity portfolio, and execution-ready roadmap.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: