Skip to content

Refactor slash commands into a Claude Code skill architecture #6

Description

@larnsce

Background

Commands and skills have converged in Claude Code; skills additionally support supporting files with progressive disclosure, frontmatter control (disable-model-invocation, allowed-tools), and cleaner packaging. Research (July 2026) found no equivalent existing implementation to borrow wholesale; the architecture is ours to design. A premortem on this refactor identified the main risks; see premortem-report-20260708-053608.html and premortem-transcript-20260708-053608.md.

Adoption/distribution by other reviewers is explicitly out of scope for now; a marketplace can come later if ever needed.

Approach

Prototype first, then convert:

  1. Convert the read-only /review-status command into a skill as a prototype. Verify firsthand rather than trusting secondhand docs: frontmatter field behavior, whether reference files resolve reliably when the skill runs from a target package directory, and context loading behavior.
  2. If the prototype holds, convert the remaining commands one skill per entry point (review-package, review-issue, create-next-issue, review-complete, create-release), each with disable-model-invocation: true so nothing auto-triggers.
  3. Move long reference material (canonical checklists from Consolidate review checklists into a single source of truth #5, templates, standard _pkgdown.yml) into skill supporting files.

Kill criterion

If the prototype cannot reliably load its reference files from a target package directory after one day of testing, stop the skill migration and keep the command files, deduplicated per #5, instead.

Tasks

  • Prototype: review-status as a skill, tested from inside a real data package repo
  • Document verified platform behavior: what frontmatter fields actually do in the installed Claude Code version
  • Convert remaining commands to skills
  • Retire commands/: replace files with deprecation stubs pointing at the skills
  • Update README install instructions

Depends on #4 and #5: do not migrate contradictory content.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions