home / skills / spm1001 / trousse / review

review skill

/skills/review

This skill initiates a comprehensive code review by invoking the titans three-lens review to improve quality and maintainability.

npx playbooks add skill spm1001/trousse --skill review

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
158 B
---
name: review
description: Code review alias. Invokes titans (three-lens review).
---

# /review

This is an alias. Immediately invoke the `titans` skill.

Overview

This skill is a code-review alias that immediately invokes the titans review flow. It provides a shortcut to run a three-lens review (architecture, correctness, and maintainability) without extra configuration. Use it when you want a focused, multi-perspective review triggered quickly.

How this skill works

When called, the skill forwards the request to the titans skill which executes a three-lens review pipeline. The titans flow inspects architecture and design, checks for correctness and bugs, and evaluates maintainability and style. Results are returned together so you get a consolidated, lens-separated assessment.

When to use it

  • Quickly request a comprehensive code review without composing multiple commands
  • Validate pull requests before merging
  • Audit critical modules for design or security issues
  • Run regular maintainability checks on legacy codebases
  • Get multi-perspective feedback during code review sessions

Best practices

  • Provide a minimal context: file paths, a short description of intent, and any tests or reproduce steps
  • Include the specific commit or diff you want reviewed to keep feedback targeted
  • If you need deeper analysis on one lens, run titans directly and pass lens-focused prompts
  • Share known constraints (performance, platform, backward compatibility) to avoid irrelevant suggestions
  • Treat the alias as a fast-entry point — refine requests with follow-ups for remediation plans

Example use cases

  • Alias a continuous integration job to trigger a three-lens review on pull requests
  • Ask for a pre-merge sanity check on a feature branch to catch design regressions
  • Run a quick audit of a security-sensitive function to expose correctness flaws
  • Use during pairing sessions to generate structured feedback you can discuss
  • Schedule periodic reviews of legacy modules to identify refactoring targets

FAQ

What exactly does the three-lens review cover?

It covers architecture and design decisions, correctness and bug detection, and maintainability including readability and code hygiene.

Can I customize which lenses run?

This alias always invokes the full titans flow. For lens-specific runs, call the titans skill directly with lens options.

Do I need to supply tests or context?

Supplying tests, usage examples, or the specific diff improves accuracy and focus, though the alias can run with just code.