Review changed TypeScript files for DRY violations and testability issues.
npx skills add https://github.com/nickstrad/veil-ai --skill polish-nickstrad
Please help me install this Agent Skill. Skill: polish Source: https://github.com/nickstrad/veil-ai/tree/main/.claude/skills/polish-branch Command: npx skills add https://github.com/nickstrad/veil-ai --skill polish-nickstrad
This Skill eliminates the risk of merging feature branches with hidden code quality issues like duplicated logic, untestable business logic, low-value tests, and inconsistent patterns that accumulate technical debt and increase long-term maintenance costs.
Invoke the polish skill to review all changed files in your current branch and receive prioritized, actionable feedback on code quality issues before merging.
High-intent search queries and answers about installing and using this skill.
To check feature branches for DRY violations and pattern inconsistencies, run an interactive code review across all changed worktree files. This process identifies duplicated logic and deviations from established repository conventions, delivering prioritized, file-specific findings with proposed fixes for explicit user confirmation.
Finding untestable business logic requires scanning for code embedded in UI components or entry points. A targeted code review identifies these sections and recommends extracting them into testable service or helper functions with optional database parameters for in-memory test injection.
To audit test quality and flag low-value tests, review changed files for tests that only assert trivial outcomes, miss meaningful edge cases, or duplicate existing coverage. This ensures every test provides clear value and eliminates unnecessary complexity before merging.
Yes, this code review approach applies to TypeScript codebases using Prisma and Zod. It checks changed files for n+1 query patterns, validates Zod schema usage, and enforces co-located test directories alongside established repository patterns to align with team standards.
Branch code review handles technical debt by delivering prioritized, file-specific findings with proposed fixes. It requires explicit user confirmation before applying any changes, ensuring all modifications align with team standards and existing utilities in src/common/ and src/db/.
DavidTejuSet up git worktrees for Next.js projects with Prisma client generation and env file copying.
TencentBlueKingMap change propagation across core bklog utility modules.
libertininickAssess test suites for quality and coverage across CI pipelines.
mikecubedDetect N+1 queries, unbounded loops, and missing pagination in code reviews.
