pr review enforcer

Security Community

Skill notes

Overview

Review code with a findings-first mindset instead of a summary-first mindset.

Core Workflow

Read the diff and the surrounding code before judging the change. Look for correctness issues first: regressions, edge cases, state handling, concurrency, data integrity, and compatibility. Check architecture and maintainability: layering, ownership boundaries, duplication, naming, and hidden complexity. Check safety gaps: missing tests, weak observability, migrations, rollout risk, secrets, and authorization concerns.

Deliver

Lead with actionable findings, ordered by severity. Include open questions only after concrete issues. Mention testing gaps and residual risk even when the diff looks sound. State explicitly when no findings are discovered.

Guardrails

Avoid generic praise or style-only comments unless they affect clarity or risk. Do not review from the diff alone when nearby code changes the meaning. Keep comments specific enough that the author can act on them quickly.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@00PrabalK00 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Pr Review Enforcer

## Overview

Review code with a findings-first mindset instead of a summary-first mindset.

## Core Workflow

1. Read the diff and the surrounding code before judging the change.
2. Look for correctness issues first: regressions, edge cases, state handling, concurrency, data integrity, and compatibility.
3. Check architecture and maintainability: layering, ownership boundaries, duplication, naming, and hidden complexity.
4. Check safety gaps: missing tests, weak observability, migrations, rollout risk, secrets, and authorization concerns.
5. Report findings in priority order with file references and concise reasoning.

## Deliver

- Lead with actionable findings, ordered by severity.
- Include open questions only after concrete issues.
- Mention testing gaps and residual risk even when the diff looks sound.
- State explicitly when no findings are discovered.

## Guardrails

- Avoid generic praise or style-only comments unless they affect clarity or risk.
- Do not review from the diff alone when nearby code changes the meaning.
- Keep comments specific enough that the author can act on them quickly.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.