Skip to content

Add ralph-review-trio skill (development category)#568

Open
hoiung wants to merge 1 commit into
davila7:mainfrom
hoiung:add-ralph-review-trio-skill
Open

Add ralph-review-trio skill (development category)#568
hoiung wants to merge 1 commit into
davila7:mainfrom
hoiung:add-ralph-review-trio-skill

Conversation

@hoiung
Copy link
Copy Markdown

@hoiung hoiung commented May 6, 2026

What this adds

A new skill at cli-tool/components/skills/development/ralph-review-trio/ containing:

  • SKILL.md — trigger conditions, output schema, per-tier semantics, install instructions
  • references/ — per-tier checklists (haiku-checklist.md, sonnet-checklist.md, opus-checklist.md) and _common-culprits.md
  • assets/example-transcript.md

What it documents

Sequential three-tier code review (Haiku surface → Sonnet logic → Opus deep) with restart-on-fail: any tier failure restarts the whole loop from Tier 1. Pass = all three tiers passed in a row against the same final state.

Why a discovery-only skill

The Ralph Review Trio is a multi-component plugin (1 command + 3 agents + 1 skill). Single-component installs via claude-code-templates --skill would only deliver the skill content, not the agent dispatch infrastructure. So this skill entry is a discovery surface: it documents the trigger semantics and expected outputs, and points users to the upstream plugin install for the full functionality:

/plugin marketplace add hoiung/sst3-skills
/plugin install ralph-review-trio@sst3-skills
/reload-plugins

This pattern is consistent with how claude-code-templates already handles cross-cutting Anthropic skills (see skills/ANTHROPIC_ATTRIBUTION.md).

Provenance

Catalog

Ran python scripts/generate_components_json.py after adding the skill. docs/components.json reflects the regenerated catalog (skills count 808 → 809).

Battle-tested

In active use since January 2026 across hoiung/dotfiles (430+ issues, ~155 closed with all three tier-pass tokens) and hoiung/auto_pb_swing_trader. Ralph has caught: a database helper returning dict-row cursors while callers indexed by [0] (eight latent bugs, one silently writing NULL foreign keys); a cache helper substituting defaults whenever callers forgot a required argument; a hardcoded repo-path assumption Ralph spotted inside its own tier checklist.


Summary by cubic

Adds the ralph-review-trio discovery skill for a three-tier code review (Haiku → Sonnet → Opus) and updates the components catalog. Documents triggers and outputs; the actual /ralph-review command ships in hoiung/sst3-skills.

  • Areas: components (cli-tool/components/), website (docs/)
  • New component: cli-tool/components/skills/development/ralph-review-trio/ with SKILL.md, references/, and an example transcript
  • Discovery-only skill; points to marketplace install in hoiung/sst3-skills for the full plugin and agents
  • Catalog: docs/components.json regenerated; no new environment variables or secrets

Written for commit 160048a. Summary will update on new commits.

Discovery entry for the Ralph Review Trio plugin. Sequential three-tier
code review (Haiku surface, Sonnet logic, Opus deep) with restart-on-fail.

The skill documents trigger conditions, expected output schema, and
per-tier semantics. The actual /ralph-review command + 3 reviewer agents
ship via the upstream marketplace install:

  /plugin marketplace add hoiung/sst3-skills
  /plugin install ralph-review-trio@sst3-skills

Source: https://github.com/hoiung/sst3-skills (MIT)
Writeup: https://hoiboy.uk/posts/shipping-ralph-review-trio/

Catalog regenerated via scripts/generate_components_json.py (skills 808 -> 809).
@vercel
Copy link
Copy Markdown

vercel Bot commented May 6, 2026

Someone is attempting to deploy a commit to the Daniel Avila's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added the review-pending Component PR awaiting maintainer review label May 6, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 6, 2026

👋 Thanks for contributing, @hoiung!

This PR touches cli-tool/components/** and has been marked review-pending.

What happens next

  1. 🤖 Automated security audit runs and posts results on this PR.
  2. 👀 Maintainer review — a human reviewer validates the component with the component-reviewer agent (format, naming, security, clarity).
  3. Merge — once approved, your PR is merged to main.
  4. 📦 Catalog regeneration — the component catalog is rebuilt automatically.
  5. 🚀 Live on aitmpl.com — your component appears on the website after deploy.

While you wait

  • Check the Security Audit comment below for any issues to fix.
  • Make sure your component follows the contribution guide.

This is an automated message. No action is required from you right now — a maintainer will review soon.

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 7 files

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

Labels

review-pending Component PR awaiting maintainer review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant