chore: add Rhiza Claude commands (/rhiza_quality, /rhiza_update) - #2
Closed
tschm wants to merge 1 commit into
Closed
chore: add Rhiza Claude commands (/rhiza_quality, /rhiza_update)#2tschm wants to merge 1 commit into
tschm wants to merge 1 commit into
Conversation
Adds two distributed Claude Code slash commands under .claude/commands/: - /rhiza_quality: run the code-quality gate and score the repo. - /rhiza_update: bump the pinned Rhiza version, sync, resolve conflicts, verify the gates, and open a PR. Injected ahead of the Rhiza release that ships them via sync; once that release is synced these become managed by the template. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds two Claude Code slash-command definitions intended to standardize Rhiza template updates and run a Rhiza-style quality gate.
Changes:
- Adds
/rhiza_qualitycommand to run a multi-step quality gate and produce a scorecard. - Adds
/rhiza_updatecommand to bump the Rhiza template pin, sync, resolve conflicts, verify gates, and open a PR.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
.claude/commands/rhiza_quality.md |
New slash command to run Rhiza quality gates and generate a scored assessment. |
.claude/commands/rhiza_update.md |
New slash command to update the pinned Rhiza template version, sync, and open an update PR. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+5
to
+9
| Assess the quality of this repo against Rhiza standards. Follow the | ||
| command-execution policy: always prefer `make <target>`; never invoke | ||
| `.venv/bin/...` directly. Run the gates in order — cheapest checks first so fast | ||
| failures surface before the slow test suite — and collect results: | ||
|
|
Comment on lines
+56
to
+67
| **Scope the scorecard to locally-owned items — not what the mother repo (Rhiza) | ||
| owns.** This project syncs its dev infrastructure from `jebel-quant/rhiza`; see | ||
| `CLAUDE.md` for the authoritative split and the `files:` block of | ||
| `.rhiza/template.lock` for the machine-generated list of synced files. Score | ||
| only what this repo actually controls — `src/`, `tests/`, `pyproject.toml`, | ||
| `README.md`, project-specific docs, `.rhiza/template.yml`, and any | ||
| locally-hardened config. Do **not** let Rhiza-managed files (the | ||
| `.github/workflows/*`, `Makefile`, `.pre-commit-config.yaml`, `pytest.ini`, | ||
| `ruff.toml`, the typecheck/mutation/fuzzing targets, etc.) drive the marks — a | ||
| gap there is fixed upstream in Rhiza, not here. If a relevant signal is | ||
| Rhiza-owned, note it as "upstream/out-of-scope" rather than scoring it against | ||
| this repo. |
Comment on lines
+5
to
+11
| Update this repo's Rhiza template to a newer release: bump the pin in | ||
| `.rhiza/template.yml`, run the sync, resolve every conflict, verify the quality | ||
| gates, and open a PR. Follow the command-execution policy: always prefer | ||
| `make <target>`; never invoke `.venv/bin/...` directly. | ||
|
|
||
| `$ARGUMENTS` may name a target version (e.g. `v0.19.1`). If empty, target the | ||
| **latest** release of the upstream template repo. |
Comment on lines
+53
to
+54
| **Conflict-marked files.** Resolve by the ownership rule (see `CLAUDE.md` and the | ||
| `files:` block of `.rhiza/template.lock` for the authoritative managed-file list): |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds two distributed Claude Code slash commands to
.claude/commands/:/rhiza_quality— run the code-quality gate (make fmt/typecheck/docs-coverage/deptry/security/test) and score the repo./rhiza_update— bump the pinned Rhiza version in.rhiza/template.yml, runmake sync, resolve conflicts, verify the gates, and open a PR.These are authored upstream in
jebel-quant/rhiza(bundles/core/.claude/commands/) and normally arrive viarhiza sync; this PR injects them now, ahead of the release that distributes them. Once that release is synced they become template-managed.🤖 Generated with Claude Code