agentleFS
TrecekTrecek/useful-claude-skills/.claude/skills/review-approach/SKILL.md

review-approach

Skill1 starsChanged 8 months agoMITView on GitHub

Research modern solutions and approaches for issues or features proposed in a report or plan. Use when user says "review approach", "review approaches", "research solutions", or wants external validation of a proposed direction.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After an investigation or plan, before committing to an approach

    line 22
  2. Very specific:

    Create files outside temp/review-approach/ directory

    line 28
  3. Distinctive:

    Use subagents with web search for parallel research

    line 31
  4. Distinctive:

    Keep findings concise and actionable

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review Approach Skill

Research modern solutions, approaches, and strategies relevant to the issues or features proposed in a report or plan. Uses web search subagents to gather external perspective and surface options the team may not have considered.

When to Use

  • User says "review approach", "review approaches", or "research solutions"
  • User wants to validate a proposed direction against current industry practice
  • User has a plan or report and wants to explore what modern solutions exist
  • After an investigation or plan, before committing to an approach

Critical Constraints

NEVER:

  • Modify any source code files
  • Create files outside temp/review-approach/ directory

ALWAYS:

  • Use subagents with web search for parallel research
  • Keep findings concise and actionable
  • Present options with trade-offs
  • Make recommendations based on technical merit and project fit
  • Tie research back to the specific problem context
  • Include source URLs for all referenced material

Workflow

Step 1: Extract Research Targets

From the report, plan, or conversation context, identify the core problems and proposed features that need external research. Break them into distinct research topics.

Step 2: Launch Parallel Web Search Subagents

Spawn general-purpose subagents (with web search) for each research topic. Each subagent should investigate:

  • What modern solutions exist for this problem class
  • How mature projects and frameworks approach it
  • Recent developments, libraries, or patterns worth considering
  • Known pitfalls and trade-offs of common approaches

Tailor the search queries to the specific technologies and constraints of the project.

Step 3: Synthesize

Consolidate subagent findings into a concise review. For each research topic:

  • What exists: The relevant modern approaches found
  • Trade-offs: Strengths and weaknesses in the context of this project
  • Relevance: How each option relates to the proposed direction

Drop anything that doesn't meaningfully inform the decision.

Step 4: Write Review

Save to: temp/review-approach/review_approach_{topic}_{YYYY-MM-DD_HHMMSS}.md

# Approach Review: {Topic}

**Date:** {YYYY-MM-DD}
**Source:** {Name of the report/plan being reviewed}

## Context
{Brief statement of the problem and what was proposed}

## Research Findings

### {Research Topic 1}
{What modern solutions exist, trade-offs, relevance to this project}

**Sources:**
- [{title}]({url})

### {Research Topic 2}
{...}

## Recommendations
{What approaches to pursue and why, based on the research}

## Key Takeaways
{Concise bullets — what matters most for the decision at hand}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.