risk-review
Performs findings-first code reviews to identify bugs, validation gaps, and deployment risks in local code.
Install
mkdir -p .claude/skills/risk-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19339" && unzip -o skill.zip -d .claude/skills/risk-review && rm skill.zipInstalls to .claude/skills/risk-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Repo-local findings-first review workflow for Zoolanding Lambda diffs, deploy candidates, and contract changes. Use when reviewing for bugs, regressions, rollout risk, weak validation, or missing tests.Key capabilities
- →Identify bugs and release risks in diffs
- →Assess deploy-readiness of lambda functions
- →Analyze request-response contract changes
- →Challenge unproven assumptions in code
- →Ground findings in concrete evidence
How it works
The workflow focuses on high-risk surfaces like validation and state transitions, requiring reviewers to provide evidence-based findings and suggest specific fixes.
Inputs & outputs
When to use risk-review
- →Review pull requests for potential bugs
- →Assess deploy-readiness of lambda functions
- →Identify missing tests or validation logic
- →Analyze changes to request-response contracts
About this skill
Risk Review
This repo-local version is for review-only work. Lead with findings, not summaries.
Review Targets
- local diffs or pull requests
- request or response contract changes
- storage, lifecycle, or payload behavior changes
- deploy-readiness and regression checks
Output Contract
Each finding should include:
- severity
- concrete failure mode
- exact file or surface when available
- the smallest useful fix direction or missing test
If there are no findings, say that explicitly and note any residual testing gap.
Review Workflow
-
Identify the intended change.
- What behavior is meant to change?
- What behavior must remain stable?
-
Inspect the highest-risk surfaces.
- request and response validation
- state transitions and persisted output
- error handling and fallback behavior
- env vars, IAM assumptions, dependency packaging, and template wiring
- tests, harness coverage, and docs drift
-
Challenge unproven assumptions.
- Missing fields, malformed payloads, stale env vars, and partial deployments matter more than the happy path.
-
Prefer evidence.
- Ground findings in code, tests, runtime output, or a concrete deploy-readiness gap.
-
Return findings in priority order.
- bugs and release risks first
- then fragile behavior or missing tests
- then lower-value clarity issues only if they affect correctness
Severity Guide
High: likely broken behavior, data loss, or release blockerMedium: works in the happy path but is fragile or untested in an important caseLow: clarity or maintainability issue with real defect riskQuestion: unresolved ambiguity that could hide a defect
When not to use it
- →When performing general code style reviews
- →When the change is not a deploy candidate
Limitations
- →Findings must be grounded in code, tests, or runtime output
- →Requires priority ordering of findings
How it compares
Unlike general reviews, this process prioritizes findings over summaries and mandates grounding every observation in concrete evidence or testing gaps.
Compared to similar skills
risk-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| risk-review (this skill) | 0 | 3mo | No flags | Advanced |
| django-verification | 5 | 4mo | Review | Intermediate |
| proof-of-work | 1 | 6mo | No flags | Intermediate |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by LynxPardelle
View all by LynxPardelle →You might also like
django-verification
affaan-m
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
proof-of-work
MadAppGang
Proof artifact generation patterns for task validation. Covers screenshots, test results, deployments, and confidence scoring.
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
test-cases
cexll
This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.
reviewing-code
CaptainCrouton89
Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.