devlyn:review

Review changed files, fix issues, and run lint and tests.

4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/fysoul17/ian-on-v1 --skill devlyn-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devlyn:review
Source: https://github.com/fysoul17/ian-on-v1/tree/main/ian-on/.claude/skills/devlyn%3Areview
Command: npx skills add https://github.com/fysoul17/ian-on-v1 --skill devlyn-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents security and quality regressions by performing a comprehensive, post-implementation review that validates changed code, then fixes issues immediately instead of only reporting them.

Core Features & Use Cases

  • Security-first CRITICAL/HIGH enforcement: Detects and resolves vulnerabilities such as hardcoded secrets, injection risks, XSS, missing boundary validation, insecure dependencies, and path traversal.
  • Quality and reliability verification: Ensures code health by running lint and the test suite, then blocks approval if lint/tests fail or critical issues remain.
  • Context-aware escalation: Escalates to a team review when changes span many files, multiple domains (UI + API + auth), or require multi-perspective judgment.

Quick Start

Perform a post-implementation review of the current changes by enumerating changed files, inspecting their contents, fixing issues directly, then running lint and tests and producing a file:line referenced summary.

Frequently Asked Questions about devlyn:review

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

FAQPage Schema
How do I automate code review and fix security vulnerabilities in a pull request?

Automated code review inspects modified changeset files to detect and fix security vulnerabilities like hardcoded secrets, XSS, and injection risks immediately. It enforces security-first boundary checks and blocks approval when CRITICAL or HIGH issues remain unresolved.

How does CI quality gate enforcement handle failing lint and test suites?

CI quality gates enforce reliability by running lint and test suites during the review process. The approval gating mechanism automatically blocks pull requests when lint checks fail or tests do not pass, ensuring code health is verified before merge.

What is the best way to review large changesets that span multiple domains like UI and API?

Reviewing large changesets spanning UI, API, and auth domains triggers context-aware escalation. This process flags multi-domain changes requiring multi-perspective judgment, routing them to a collaborative team review instead of relying solely on automated fixes.

Can I use automated code review for incremental PRs across both UI and API layers?

Yes, automated code review is designed for software teams validating incremental PRs across UI and API layers. It enumerates changed files, repairs discovered issues directly, and generates a file:line referenced summary for thorough post-implementation validation.

What types of security issues does a security-first code review detect and resolve?

Security-first code review detects and resolves vulnerabilities including hardcoded secrets, injection risks, XSS, missing boundary validation, insecure dependencies, and path traversal. It repairs these discovered issues immediately to prevent security regressions.

When should I expect a code review to block my pull request approval?

Code review blocks pull request approval when any CRITICAL or HIGH security issues remain unfixed, or when lint and test suites fail. This approval gating ensures no security or quality regressions are introduced into the codebase.