CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check, analyze impact on plugin (breaking changes, opportunities, deprecations). Run periodically or before releases. NOT part of the distributed plugin.
CONTRIBUTOR TOOL - Check the plugin against current cached Claude Code docs. Use before releases or after Claude docs changes to separate real schema drift from stale local assumptions. Not part of the distributed plugin.
Guide plugin development workflow for this repo. Use when editing shipped plugin files under plugins/ruby-grape-rails/, release/docs metadata, or contributor tooling under .claude/.
Deep qualitative review of high-signal sessions. Use after /session-scan to inspect transcripts, validate heuristic metrics, and synthesize contributor-facing findings.
Compute exploratory metrics for recent Claude sessions. Deterministic SQLite-direct scan over the local ccrider database; no MCP, no LLM, no subagents for scoring.
Analyze exploratory trends across the session metrics ledger. Use for provider-scoped comparisons and broad monitoring, not for release-grade conclusions.
Analyze observational skill-effectiveness signals across scanned sessions. Use for exploratory monitoring and recommendation triage, not as a release gate.
Active Record patterns: models, queries, associations, transactions, locking, migrations. Triggers: "AR scope", "hasmany through", "polymorphic". Do NOT use for: Sequel, N+1.
Running a project-wide audit of a Ruby/Rails/Grape codebase: architecture, security, performance, testing coverage, ops risk. Emits findings to .claude/audit/.
Exploring approaches, comparing options, and gathering requirements for a vague Ruby/Rails/Grape feature idea before /rb:plan. Interview-style discovery; emits interview.md.
Capturing a solved Ruby/Rails/Grape problem as reusable knowledge. YAML solution doc. Triggers: "compound this", "save this solution", "capture this fix".
Drafting an anonymized GitHub-issue-ready report from verify-output compression telemetry: PII-redacted, actionable, user copies into a maintainer issue.
Running the end-to-end Ruby/Rails/Grape lifecycle in one shot: plan → work → verify → review → compound, chained. Autonomous on happy path; halts on /rb:verify --full failure (HALTEDVERIFYFAILED), BLOCKED review (HALTEDREVIEWBLOCKED), REQUIRES CHANGES review (HALTEDREVIEWREQUIRESCHANGES), or unparsable review…