Review completed code against project plans and coding standards.
npx skills add https://github.com/jacexh/skills --skill code-reviewer-jacexh
Please help me install this Agent Skill. Skill: code-reviewer Source: https://github.com/jacexh/skills/tree/main/skills/code-reviewer Command: npx skills add https://github.com/jacexh/skills --skill code-reviewer-jacexh
Projects often diverge from their original plans or coding standards during implementation, leading to subtle architecture regressions, security issues, insufficient tests, and undocumented design decisions. This Skill provides a structured, senior-level review to quickly identify deviations, prioritize fixes, and verify that completed work satisfies the project's intent and quality bar.
Review the completed feature implementation against the original plan and coding standards and return a structured report listing Critical, Important, and Suggestion issues with examples and recommended fixes.
High-intent search queries and answers about installing and using this skill.
To review code against project plans and coding standards, compare the completed implementation to the original plan and flag unjustified deviations. This structured review evaluates architecture, error handling, security, performance, and test coverage to produce categorized findings with recommended fixes.
Checking pull requests for architecture regressions and security issues requires a senior-level review assessing separation of concerns, SOLID principles, and defensive programming. The process categorizes findings into Critical, Important, and Suggestion tiers with actionable examples before merge or release.
A structured code review verifies test coverage and documentation by evaluating inline comments, function headers, and adherence to project-specific conventions. It checks naming, organization, and test completeness to ensure completed work satisfies the project's quality bar.
Yes, you can use an automated review to prioritize fixes for undocumented design decisions. It identifies insufficient tests and undocumented design choices, then outputs a prioritized report categorizing findings as Critical, Important, or Suggestions with specific examples and recommended fixes.
Yes, this code review process works for completed feature branches before merge. Running on a completed feature branch or pull request produces a prioritized review report assessing architecture, tests, and documentation to verify the implementation satisfies the project's intent.
Implementations diverge from original plans during feature development due to subtle architecture regressions, security issues, insufficient tests, and undocumented design decisions. A structured review identifies these deviations, prioritizes fixes, and verifies completed work against the project's intent.
christopher-bussReview code changes against coding standards and project specifications.
peancharoenReview git diffs and file paths for code issues with severity labels.
jonmummReview codebases for SOLID and separation of concerns adherence.
inbharataiAnalyzes code for bugs, security vulnerabilities, performance bottlenecks, and style violations.
