Skip to content

chore: add /check-rs skill to repo for shared use#20

Merged
lionelle merged 1 commit into
mainfrom
chore/add-check-rs-skill
Jun 15, 2026
Merged

chore: add /check-rs skill to repo for shared use#20
lionelle merged 1 commit into
mainfrom
chore/add-check-rs-skill

Conversation

@lionelle

Copy link
Copy Markdown
Contributor

What

Vendors the /check-rs Rust quality-pass skill into the repository at
.claude/skills/check-rs/SKILL.md so it ships with the repo. Previously this
skill only existed in individual contributors' local ~/.agents/skills
directory; committing it makes /check-rs available to anyone who clones this
repo.

The skill

/check-rs performs a comprehensive quality pass on recently changed Rust code:

  1. Toolingcargo fmt + cargo clippy -- -D warnings (fixes before reviewing)
  2. Review agents (parallel) — DRY/organisation, complexity/docs, and test-coverage reviews of the diff
  3. Fix-up — applies every finding (no bare #[allow(...)] suppressions)
  4. Verificationcargo fmt --check, cargo clippy -- -D warnings, cargo test must all pass

Verification

This change is docs/tooling only (no Rust source touched). Ran the skill's
tooling + verification phases against the project to confirm it's clear:

  • cargo fmt --check — clean
  • cargo clippy --all-targets -- -D warnings — 0 warnings
  • cargo test — 140 tests + 9 doc-tests passing, 0 failed

🤖 Generated with Claude Code

Vendor the check-rs Rust quality-pass skill (fmt, clippy, DRY/complexity/test
review agents, then fix-up) into .claude/skills so every contributor using this
repo has /check-rs available without local agent setup.

Verified clean before commit: cargo fmt --check, cargo clippy --all-targets
-- -D warnings (0 warnings), cargo test (140 + 9 doc-tests passing).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@lionelle lionelle merged commit 4dcacca into main Jun 15, 2026
4 checks passed
@lionelle lionelle deleted the chore/add-check-rs-skill branch June 15, 2026 02:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant