Add Claude commands from shrinkage repo#4
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughAdded three ChangesRhiza command docs
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Adds three Claude Code slash-command definitions under .claude/commands/ to help run Rhiza-related workflows (book build, quality assessment, and template sync/update) from within Claude Code.
Changes:
- Introduce
/rhiza_updateworkflow instructions for bumping.rhiza/template.yml, syncing, resolving conflicts, and verifying gates. - Introduce
/rhiza_qualityworkflow instructions for running Rhiza quality gates and producing a scorecard. - Introduce
/rhiza_bookworkflow instructions for building and serving the MkDocs/zensical book locally.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
.claude/commands/rhiza_update.md |
New slash command doc for updating/syncing the Rhiza template and validating gates. |
.claude/commands/rhiza_quality.md |
New slash command doc for running quality gates and producing a scoped scorecard. |
.claude/commands/rhiza_book.md |
New slash command doc for building and locally serving the documentation book. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| --- | ||
| description: Update the pinned Rhiza version in .rhiza/template.yml, sync, resolve conflicts, and verify | ||
| --- |
| **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): |
| - **Rhiza-managed files** (the `.github/workflows/*`, `Makefile`, | ||
| `.pre-commit-config.yaml`, `pytest.ini`, the `.rhiza/` engine, etc.): take the | ||
| **incoming/upstream** side — these are owned by the template and should match | ||
| it (`git checkout --theirs -- <file>` then `git add`). | ||
| - **Locally-owned or locally-hardened files** (notably `ruff.toml`, plus | ||
| `pyproject.toml`, `README.md`, `src/`, your `tests/`): **merge by hand** — |
| --- | ||
| description: Run the Rhiza code-quality gate and score the repo (lint, types, docs, deps, security, tests) | ||
| --- |
| **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`, |
| 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 |
| for the built folder **in the background** so it does not block the session: | ||
|
|
||
| ``` | ||
| (cd _book && uv run python -m http.server 8000) | ||
| ``` |
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
98f91f2 to
1b17bd5
Compare
|
Superseded by alihaskar#39, which targets the upstream repo. |
Adds the three Claude slash commands from the shrinkage repo:
/rhiza_book/rhiza_quality/rhiza_update🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Documentation