smithery/brendankowitz

technical-review

Conduct a detailed technical review of recent changes or a specific feature. Use when user says "review PR", "code review", or "review [scope]". Analyzes for logic errors, bugs, style issues, and performance. Fixes critical/high issues automatically.

Installation

$ npx skills add smithery/brendankowitz --skill technical-review

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/brendankowitz.

npx skills add smithery/brendankowitz

Browse all from smithery/brendankowitz

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,757 B
  • docs SUMMARY.md 274 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Technical PR Review

Conduct a detailed technical review of recent changes or a specific feature, focusing on logic, bugs, code style, and performance. Research false positives and apply fixes for critical and high-priority items.

Usage: When user says "review PR", "code review", or "review [scope]"

Instructions

  1. Analyze Changes:

- Use GitHub CLI (gh) or GitHub MCP tools if available to fetch PR diffs, comments, and conversation history. - Identify new or modified code. - Review for logic errors, edge cases, and potential bugs. - Evaluate against project coding standards and style guides. - Check for potential regressions or performance bottlenecks.

  1. Handle Findings:

- Research False Positives: Verify if flagged issues are genuine bugs or intentional implementations. - Prioritize: Categorize findings into Critical, High, and Medium. - Next steps: Always provide actionable next steps.

  1. Remediate:

- Fix Criticals: Automatically attempt to fix verified "Critical" and "High" priority technical issues (delegate to appropriate coding agent). - Comment: Provide feedback on "Medium" or stylistic items.

  1. Verify:

- Ensure the build passes after fixes. - Verify that tests cover the new logic.

Scopes

  • (default): Review changes in the current working branch/directory.
  • {feature-name}: Review code within a specific feature folder.