From sandi
Installs the Sandi Metz automated PR-review GitHub workflow into the current repository, copying a template and optionally scoping review to specified path globs.
How this command is triggered — by the user, by Claude, or both
Slash command
/sandi:install-review path glob(s) to scope the review to (optional) e.g. app/** lib/**The summary Claude sees in its command listing — used to decide when to auto-load this command
Install the Sandi Metz automated PR review workflow into this repository. The
workflow runs `claude-code-action` on every opened/reopened PR (and on `/sandi`
PR comments), installs the `sandi` plugin from the jebs-dev-tools marketplace
into the CI runner, and delivers the review as inline PR comments plus one
summary comment.
The generic template lives at `${CLAUDE_PLUGIN_ROOT}/templates/sandi-review.yml`.
Follow these steps:
1. **Verify the repo.** Confirm the current directory is a git repository with
a GitHub remote (`git remote -v`). If not, stop and explain that the
workflow o...Install the Sandi Metz automated PR review workflow into this repository. The
workflow runs claude-code-action on every opened/reopened PR (and on /sandi
PR comments), installs the sandi plugin from the jebs-dev-tools marketplace
into the CI runner, and delivers the review as inline PR comments plus one
summary comment.
The generic template lives at ${CLAUDE_PLUGIN_ROOT}/templates/sandi-review.yml.
Follow these steps:
Verify the repo. Confirm the current directory is a git repository with
a GitHub remote (git remote -v). If not, stop and explain that the
workflow only works on GitHub-hosted repos.
Check for an existing install. If .github/workflows/sandi-review.yml
already exists, show the user how it differs from the template and ask
before overwriting.
Copy the template to .github/workflows/sandi-review.yml (create the
directory if needed).
Scope the review (optional). If the user passed path globs as arguments, or asks to limit the review to part of the codebase:
paths: filter under the pull_request trigger with those globs
(replace the commented example).Scope: paragraph in the prompt to say the review covers ONLY
changed files matching those paths and ignores changes elsewhere.If no scope was given, leave the template as-is — it reviews all changed files in the PR.
Verify the secret. Run gh secret list and check for
CLAUDE_CODE_OAUTH_TOKEN. If it's missing, tell the user to create one:
claude setup-token # generates an OAuth token (requires a Claude subscription)
gh secret set CLAUDE_CODE_OAUTH_TOKEN
Summarize. Tell the user: the workflow file installed, how it triggers
(auto on PR open/reopen; /sandi comment from an owner/member/collaborator
for a re-review), any scoping applied, and whether the secret is in place.
Offer to commit the workflow file — but do not commit without their say-so.
$ARGUMENTS
npx claudepluginhub el-feo/ai-context --plugin sandi/install-reviewInstalls the Fowler refactoring PR-review GitHub workflow into the current repository, optionally scoped to path globs.
/pipelineAdds and validates one CI/CD workflow bundle at a time for GitHub Actions (code quality, build/test, security, integration, operations). Supports --dry-run, --skip-install, --pr flags.
/setup-github-actionsAnalyzes the project and generates production-ready GitHub Actions workflows using the Claude Code action, with proper permissions, tool scoping, and canonical filenames.
/code-reviewReviews a pull request in the SMILE-factory monorepo, producing a single advisory review (approve or comment) via GitHub CLI. Skips drafts, planning docs, and doc-only changes.
/cc-cicdGenerates, audits, or templates CI/CD workflows for GitHub Actions, GitLab CI, or Azure Pipelines, integrating Claude Code for PR reviews, testing, code generation, and security scanning.
/code-reviewerReviews GitHub pull requests using GitHub CLI: fetches details and diffs, analyzes files against PR template or standard criteria, drafts comments with importance levels, optionally validates with Codex, posts to PR.