← ClaudeAtlas

tendril-reviewlisted

Comprehensive post-change review of all modified files. Checks for code smells, cleanup opportunities, unnecessary legacy support, missing tests, broken tests, and obsolete tests. Use after a big change to leave the codebase in better health.
Ivy-Interactive/Ivy-Tendril · ★ 150 · Code & Development · score 70
Install: claude install-skill Ivy-Interactive/Ivy-Tendril
# tendril-review Perform a thorough review of all changes in the current working tree (or a specified branch/PR). The goal is to leave every touched file in better code health than before. ## Invocation ``` /tendril-review ``` No arguments required — operates on the current git diff against the base branch. ## What This Skill Does 1. Identifies ALL changed files (staged, unstaged, and committed on branch) 2. Reviews each file for code smells, cleanup opportunities, and quality issues 3. Flags unnecessary legacy/backwards-compatibility code (asks before removing) 4. Checks test coverage — missing tests, broken tests, obsolete tests 5. Runs the test suite and reports failures 6. Produces actionable recommendations ## Execution Steps ### Phase 1 — Scope the Changes 1. Run `git diff --name-only` against the base branch to get all changed files 2. Run `git status` to capture any uncommitted changes 3. Categorize files: source code, tests, config, promptware, other 4. Flag any files that seem unrelated to the main change — **ask the user** if there's confusion about why they changed ### Phase 2 — Code Quality Review For each changed source file: 1. Read the full file content 2. Check for: - Dead code or unused imports - Code duplication - Overly complex methods (consider cyclomatic complexity) - Poor naming or unclear intent - Missing error handling at system boundaries - Inconsistent patterns vs. the rest of the codebase - Unnecessary abstractions