skills.rest
Simon-YHKim
Simon-YHKimCOMMUNITY
Explore all skills by this author →
GitHub

review

Reviews code changes and produces severity-prioritized feedback with actionable fix suggestions.

Updated Apr 5, 2026
Search Tags:#static analysis#code review#pull request#dead code#unused imports#git diff#pre-merge
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill review-simon-yhkim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/review
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill review-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ts-unused-exports, typescript, autoflake, and includes scripts (resource) components.

What problem does it solve? Code reviews often miss critical issues or drown in nitpicks. This Skill structures the review process so correctness, security, and maintainability problems are caught systematically and reported by severity before merge. ## Core Features & Use Cases - Scoped Review: Reviews uncommitted changes, branch diffs against main, specific files, or PR diffs fetched via GitHub MCP tools. - Severity-Prioritized Reports: Groups findings into blocking, should-fix, and nit categories, each citing file path, line number, and a concrete fix. - Pre-Merge Cleanup Scan: Runs an automated script to detect dead code, unused imports, and orphaned files across TypeScript, JavaScript, Python, and Go before merging. - Use Case: Before merging a feature branch, ask for a review to get a checklist of dead code, unused imports, and logic errors with exact file locations. ## Quick Start Ask the assistant to review the current branch changes against main and report any blocking issues before merge.

Frequently Asked Questions about review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code changes before merging a pull request?▼

Run a structured review over the branch diff against main, checking correctness, security, maintainability, and tests. Findings are grouped into blocking, should-fix, and nit categories with file paths, line numbers, and concrete fixes.

How to detect dead code and unused imports in TypeScript?▼

Use ts-unused-exports to find unused exports and tsc with --noUnusedLocals to flag unused variables and imports. The pre-merge scan script runs both automatically when a tsconfig.json is present.

What tools find unused Python imports automatically?▼

autoflake with --check --remove-all-unused-imports detects unused Python imports, while vulture or pyflakes find dead code. The scan script runs autoflake when Python files exist in the source directory.

Does the pre-merge scan work without Node.js or Python installed?▼

The scan script is best-effort and skips checks when tooling is missing. It verifies npx, tsconfig.json, python3, and autoflake availability before running each check, so partial scans still produce useful results.

When should I run a pre-merge cleanup scan?▼

Run it immediately before merging a PR, after the review is approved. Dead code and orphaned files become harder to track after merge, so this final pass catches leftover commented blocks, unused imports, and stale test files.

Related Skills

Explore More Software Engineering Skills→
dwaynepartondwayneparton
1

simplify

Reviews changed code on the current branch for reuse, quality, and efficiency, then fixes issues found.

Community
Intermediate
GDSDNGDSDN
3

qa-backlog-add-followup

Create prioritized, tagged QA follow-up items linked to project backlog stories.

Community
Intermediate
uzumaki-incuzumaki-inc

health

Run code health checks and compute a weighted 0-10 score.

Official
Advanced
BluMintIncBluMintInc
2

automated-review-addressing

Automate pull request review feedback by updating the PR head branch.

Official
Advanced