Security & Regressions Code Reviewer
Verified SecureFeaturedCreated by Staff Security Guild•security Workflow
Senior engineer review stance prioritizing security flaws, off-by-one bugs, and missing tests.
npx askills install code-reviewer
Overview & Problem Solved
When modern frontier LLMs (like Claude 3.7, GPT-4o, or deep reasoning agents) execute complex domain tasks without standard operating procedures, they frequently suffer from context drift, incorrect CLI arguments, or non-standard file hierarchies. Security & Regressions Code Reviewer eliminates probabilistic guessing by supplying the Agent with an authoritative, sandboxed execution specification.
By packaging verified workflows into a structured SKILL.md manifest, this skill establishes deterministic boundaries, verifies dependencies, and executes tasks using proven engineering conventions.
Core Capabilities & Guarantees
Follows pre-tested instructions and step-by-step algorithms, avoiding experimental or hallucinated flags.
Runs with identical behavioral fidelity across OpenAI Codex, Claude Code, Cursor IDE, and Windsurf Cascade.
Enforces workspace-scoped file mutations and shields environment secrets against accidental prompt leakage.
Automates test verification, linter checks, and syntax validation before completing any user turn.
Agent Execution Pipeline
Intent Matching & Context Ingestion
The agent scans the user request against the skill's YAML frontmatter triggers and loads the verified instructions into active working memory.
Toolchain & Dependency Validation
The runtime verifies that necessary tools, interpreters, and environment configurations exist within the workspace sandbox before proceeding.
Deterministic Execution & Delivery
The agent executes the codified SOP, runs verification checks, and outputs high-fidelity deliverables without extraneous narration.
Validated Prompt Templates
(Click to copy)“Review my recent git commits on branch feat/payment-webhooks for race conditions and idempotent handling.”
“Perform a security audit on api/auth/login.ts focusing on timing attacks and token expiry.”
“Review our Prisma schema changes for missing indexes on foreign keys.”
Automated Security & Audit Report
Read-Only
Zero disk writes permittedBundled Scripts
Runs internal verified helpersOffline Sandbox
No internet egressNone Required
Runs fully standaloneEnterprise & Production Use Cases
Frequently Asked Questions
Q: What makes Security & Regressions Code Reviewer different from a standard MCP server?
MCP (Model Context Protocol) provides external protocol connections to databases or APIs. In contrast, Security & Regressions Code Reviewer is a high-level operational skill (SKILL.md) that teaches AI Agents procedural intelligence, deterministic step-by-step SOPs, parameter constraints, and self-correction workflows.
Q: Is Security & Regressions Code Reviewer compatible with frontier models like Claude 3.7 Sonnet, GPT-4o, and DeepSeek-R1?
Yes. The skill is packaged with standard markdown instructions (SKILL.md) and YAML frontmatter, adhering to the universal agent skill standard natively supported across Codex, Claude Code, Cursor, and Windsurf.
Q: What permissions does Security & Regressions Code Reviewer require in agent mode?
Every listed skill undergoes automated static analysis scoring 100/100. It strictly adheres to workspace-scoped filesystem boundaries and does not execute untrusted remote code.
Q: Can our team customize or extend the rules in this SKILL.md?
Yes. Once installed in your project root (.skills/code-reviewer/SKILL.md or ~/.agents/skills/code-reviewer/), you can customize the instructions to include internal team guidelines, custom linters, or proprietary APIs.
SKILL.md Source Specification
--- name: "code-reviewer" description: "Senior engineer code review stance prioritizing bugs, security vulnerabilities, behavioral regressions, and missing tests." --- # Senior Code Reviewer Skill Provides actionable, grounded code reviews. ## Review Stance 1. Findings First: Prioritize findings by severity (P0 Blocker, P1 Critical, P2 Edge Case). 2. Grounded References: Always cite exact file path and line numbers. 3. No fluff: Skip generic praise. Provide exact replacement diffs.