charon
Ferry a GitHub PR to merge — one snapshot-not-block iteration that reads live PR state, classifies it, and runs exactly one handler: fix CI at the root cause, repair merge conflicts, triage reviewer threads with version-currency checks, rewire human-blocked reviews, or propose-and-pause before any force op. Use when asked to merge / land / babysit a GitHub PR — including plain-language 'merge my PR', 'get this branch merged', or 'babysit my PRs' with no slash command and no state file yet — or when resuming a /charon ferry, without ever waiting forever.
derot
Truth-drift auditor — find & fix comment/doc/CI/version/dependency rot that contradicts the current code, with root + transitive verification (correct beats delete). Use when the user wants to remove stale comments, fix doc drift (CLAUDE.md/README/CHANGELOG), modernize CI publish auth, sync package versions, or question why a sub-library is used instead of a parent/successor package. Triggers on \"stale comments\", \"derot\", \"doc rot\", \"comments are out of date\", \"docs don't match the code\", \"clean up the docs\", \"why this dependency\", \"überarbeitung\".
binlog-failure-analysis
>
ci-analysis
>
ci-crash-dump
>
flow-analysis
>
elegance-pipeline
Run a persistent multi-agent workflow scoring source-file code quality: 4 scouts, 2 judges, a planner, a verifier, and 1 gated implementer. Use when you want to rank how clean a repo's files are and convert the weakest into gated refactor work. Triggers on \"find ugly files\", \"review code quality\".
test-arcade
>
review
Strict evidence-based maintainability review of a repository or diff. Read, search, compare, and trace only — never modify. Use when you want findings gated by >85% confidence and repository evidence, with strict scope control and no speculative architecture. Invoked as /nihil:review.
release
Release-gate workflow with strict CI and publishing discipline. Inspects the repository's release workflow, verifies versioning and CI state, and refuses to publish when checks are red or unknown. Blocks force-push/hard-reset/rm -rf. For NuGet, applies trusted-publishing rules. Invoked as /nihil:release.
raze
Root-authority, write-capable transformation of a repository you own — the Touch of God as one line. Full rewrite, public-API break, subsystem replacement, and deletion are pre-authorized; compatibility ceremony is skipped because the consumers are CI bots and your own framework. Keeps exactly two brakes: never leak a secret, never run a catastrophic unrecoverable command. Use when you want to transform your own framework end-to-end without permission friction. Invoked as /nihil:raze.
absence-of-value-and-meaning-code-quality-review
Review code for extreme implementation ambition without tolerating accidental complexity. Reward code that is hard, powerful, and sophisticated only when it stays readable, cohesive, loosely coupled, expressive, and semantically named. Penalize redundant code extractable into meaningful private helpers, missed refactoring, giant or fragmented files outside the 500-1000 line range, vague abstractions, noisy comments, fake simplicity, meaningless over-extraction, under-extracted logic, duplicated intent, unstable APIs, and any structure that fails to justify its complexity. Use for absence-of-value-and-meaning reviews where the target is astonishingly simple code, not simplistic code.
nihil
Last-resort first-principles repository transformation run as a pantheon of dynamic workflows, where no artifact has intrinsic preservation value and every no-op, patch, deletion, public-API break, or rebuild must be justified by evidence. Use for Nihil, first-principles transformation, aggressive architectural simplification, destructive code cleanup, public API redesign, dead-code evaporation, codebase rescue, or last-resort remediation. Routes to the /nihil, /nihil-maat, /nihil-odin, /nihil-shiva, and /nihil-athena workflows.
implement
Implement evidence-backed Nihil findings within a fixed scope, preserving behavior unless authorized. Modifies only scoped files and runs checks before claiming done. Blocks push/tag/publish/version-bump (those belong to release). Use after /nihil:review to apply findings. Invoked as /nihil:implement.
reviewing-testability
Diagnose why a module is hard to verify and fix the narrowest seam. Use when specs need heavy mocking, break on refactor, or survive plausible mutations — find missing DI seams, hidden state, temporal coupling, raw clocks. Triggers on "tests are brittle", "mocks everywhere", "too coupled".
mutation-resistant-coverage
Close branch gaps with high-signal specs, not cosmetics. Use when you run a file to 100% branches or kill survivors from Stryker/Infection/Pitest/Mutmut. Lists semantic branches and writes one real check per outcome. Triggers on "uncovered branches", "cover this file", "mutation run".
judging-test-quality
Grade and review an existing spec suite for kill power before adding more. Use when you must find whether specs are real or cosmetic — each gets STRONG/ACCEPTABLE/WEAK/KILL plus one mutation it survives. Triggers on "audit these tests", "how strong is this", "mutation score", "green but buggy".
improving-weak-tests
Rewrite a weak unit spec into one that kills mutations. Use when you must fix a toBeTruthy/toBeDefined/toBeFalsy assertion, a bare mock-fired check, an array-length-only check, a shapeless snapshot, or a private-state peek. Triggers on "rewrite this spec", "stronger assertions", "catch mutations".
x-twitter-scraper
Use when the user needs X/Twitter data through Xquik for REST API planning, MCP setup, SDKs, search, exports, monitoring, webhooks, or confirmation-gated publishing.
tomevault-publish
Publish a Skill, config, or plugin to TomeVault as a high-grade Tome — and understand the Skill / Tome / AGENTS.md model behind it. Use when shipping instruction files to TomeVault, indexing a repo, aiming for a Gold grade, passing the TomeVault scan or validator, or answering "what is a Tome / Skill / AGENTS.md". Covers the npx tomevault CLI, the Studio web publish flow, and the grading rubric.
opensrc-research
Fetch and search a dependency's real source before answering, not guessing. Use when checking what a third-party package (npm, PyPI, NuGet, crate, GitHub repo) actually does. Triggers on "how does X work", "verify Y's API", "does Z ship with W", "grep X in <library>", or any shaky dependency claim.
html-effectiveness
Produce a single self-contained .html file instead of a wall of markdown when the user wants a report, dashboard, triage board, design doc, code review, flowchart, slide deck, postmortem, implementation plan, prompt tuner, feature-flag editor, or an agent-spawn deck (HTML carrying ready-to-paste prompts for parallel fan-out) — any artifact that benefits from layout, interaction, drag-drop, side-by-side comparison, or copy-to-clipboard export. Use when the user asks (English OR German, case-insensitive, typo-tolerant, semantic, NOT literal): "html instead of markdown", "make me a dashboard", "html report", "triage board", "status report", "wochenbericht", "postmortem", "implementierungsplan", "side by side", "vergleiche x y z", "code review", "slide deck", "präsentation", "feature flag editor", "spawn agents", "agenten spawnen". Fire eagerly when the output would otherwise be a long markdown table or a sortable/filterable list. Match on intent: tickets→triage-board, diff→code-review.
temp-skill
Minimal plugin skill fixture. Use when a cc-plugin-eval test needs a tiny bundled skill.
minimal-skill
A minimal Claude Code skill fixture for cc-plugin-eval tests. Use when running cc-plugin-eval against a tiny but well-formed skill.
alpha
Alpha fixture skill. Use when cc-plugin-eval tests need one of two bundled Claude Code skills.
beta
Beta fixture skill. Use when cc-plugin-eval tests need the second bundled Claude Code skill in the multi-skill-plugin fixture.
cc-plugin-eval
Analyze, lint, and check a local Claude Code add-on or capability, explain the result, and rank the top fixes first. Use when the user says "audit this", "why did it score that way", "what should I fix first", "validate the manifest", "lint the hooks", or "benchmark the real token usage".
evaluate-plugin
Audit a local Claude Code bundle that has .claude-plugin/plugin.json: validate the manifest, lint hooks, check mcp/lsp servers, monitors, and agents, then rank fixes. Use when the user says "audit this", "validate the manifest", "lint the hooks", "why did it score that way", or "benchmark this".
improve-skill
Convert cc-plugin-eval findings into a concrete rewrite brief, then hand off to skill-creator for the edit pass. Use when the user already ran an evaluation and now wants a fix plan, after asking "what should I fix first" or "rewrite this using the findings".
known-issue-history
>
flow-tracing
>
helix-investigation
>
maestro-cli
>
pipeline-investigation
>
plugin-creator
Comprehensive guide for creating Claude Code plugins with commands, agents, skills, hooks, and MCP servers. Use when users want to create, modify, or understand plugins, marketplaces, or any plugin components.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
hotwire-patterns
Analyzes and recommends Hotwire patterns including Stimulus controllers, Turbo Frames, Turbo Streams, ActionCable broadcasts, and progressive enhancement for Rails frontends. Use when building interactive UI, partial page updates, real-time features, or form enhancements. NOT for REST API JSON responses, GraphQL, server-only background jobs, or model/database design.
rails-api-patterns
Analyzes Rails API controllers, serializers, and endpoint design for best practices. Use when building RESTful API endpoints, implementing JWT authentication, designing JSON response structures, adding API versioning, writing serializers, setting up error handling, or adding pagination and rate limiting. NOT for HTML views, Turbo/Stimulus interactions, or GraphQL schemas.
project-conventions
Detects project-specific coding conventions by scanning the codebase — service object style, auth implementation, testing patterns, custom base classes, error handling, job conventions, serialization, frontend setup. Use when generating code that must match the project's existing patterns. Always check CLAUDE.md for intent that overrides detected conventions — CLAUDE.md documents where the project is going; the fingerprint documents where it is now. NOT for stack profile classification (use rails-stack-profiles).
rails-architecture-patterns
Provides architectural planning, design decisions, and coordination guidance for Rails applications. Use when planning new features, choosing between design approaches (STI vs polymorphic, service vs concern, monolith vs engine), evaluating system architecture, or deciding which domain skill or agent to delegate to. NOT for implementation details within a single domain (use the domain-specific skill instead).
rails-auth-patterns
Authentication patterns for Rails applications. Automatically invoked when working with user login, signup, sessions, password resets, token authentication, has_secure_password, Devise, or auth configuration. Triggers on "authentication", "auth", "login", "signup", "session", "password", "has_secure_password", "Devise", "current_user", "sign_in", "sign_out", "remember me", "password reset", "email confirmation". NOT for authorization/permissions (use controller patterns for Pundit) or API token auth (use rails-api-patterns for JWT).
rails-caching-patterns
Caching patterns for Rails applications including fragment caching, low-level caching, HTTP caching, Russian doll caching, and cache invalidation strategies. Automatically invoked when working with Rails.cache, cache stores, stale?/fresh_when, fragment caching, cache keys, or performance optimization through caching. Triggers on "cache", "caching", "Rails.cache", "fragment cache", "Russian doll", "stale?", "fresh_when", "cache key", "cache store", "Redis cache", "Solid Cache", "memcached", "ETag", "cache invalidation", "cache bust". NOT for CDN configuration (use rails-devops-patterns) or database query optimization (use rails-model-patterns).
rails-controller-patterns
Analyzes and recommends Rails controller patterns including RESTful design, strong parameters, before_actions, response handling, and routing. Use when building controllers, defining routes, handling params, or managing request/response flow. NOT for model validations, service object internals, view templates, or background job logic.
rails-devops-patterns
Analyzes Rails deployment, infrastructure, and production configuration for best practices. Use when setting up Docker, writing CI/CD pipelines, configuring Puma, adding monitoring or logging, hardening security (SSL, Rack::Attack, headers), optimizing database config, or reviewing production environment files. NOT for application business logic, model design, or test writing.
rails-graphql-patterns
Analyzes and recommends GraphQL patterns for Rails using graphql-ruby including schema design, types, resolvers, mutations, subscriptions, DataLoader, and query complexity. Use when building GraphQL APIs, defining types, writing mutations, optimizing N+1 queries, or structuring app/graphql. NOT for REST API controllers, ActiveRecord queries outside GraphQL, or Turbo Stream responses.
rails-jobs-patterns
Analyzes and recommends ActiveJob background processing patterns including idempotency, retry strategies, batch processing, scheduled jobs, and queue management. Use when creating background jobs, configuring Sidekiq, handling async workflows, or optimizing job performance. NOT for synchronous controller actions, model callbacks, service object design, or real-time Turbo Streams.
rails-mailer-patterns
Action Mailer patterns for Rails applications. Automatically invoked when working with email delivery, mailer classes, email templates, mailer previews, interceptors, or delivery configuration. Triggers on "mailer", "email", "ActionMailer", "deliver_later", "deliver_now", "mail template", "email preview", "SMTP", "SendGrid", "Postmark", "notification email". NOT for push notifications, SMS, or in-app messaging.
rails-service-patterns
Analyzes and recommends Rails service object patterns for business logic extraction including command objects, result objects, form objects, query objects, and external API integration. Use when extracting logic from controllers/models, orchestrating multi-step workflows, or organizing app/services. NOT for simple CRUD, model validations, controller routing, or background job scheduling.
rails-stack-profiles
Detects a Rails project's architecture axes — logic placement (native vs extracted) and delivery (html vs api) — so other skills load profile-appropriate guidance without inline conditionals. Use when planning architecture or when a recommendation depends on where business logic lives or whether the app renders HTML or serves JSON. NOT for test framework, job backend, cache store, or auth library choices — those are orthogonal facts detected by project-conventions.
rails-testing-patterns
Analyzes Rails test suites and recommends testing best practices for RSpec and Minitest. Use when writing new tests, reviewing test coverage, fixing flaky tests, improving test performance, choosing between test types (unit, integration, system, request), or setting up factories and fixtures. NOT for production monitoring, deployment verification, or load/stress testing infrastructure.
Page 1238 of 1717 · 85820 results
