Fail-closed review of one small committed diff against its issue, structured plan, scoped guidance, and verification results. Use for the final Qwen Solve review before any branch push or pull request.
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add elixpo/elixpo_chapter --skill review-bounded-diff --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Review Bounded Diff?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/elixpo-review-bounded-diff)More formats (shields.io, HTML) on the badges page.
---
name: review-bounded-diff
description: Fail-closed review of one small committed diff against its issue, structured plan, scoped guidance, and verification results. Use for the final Qwen Solve review before any branch push or pull request.
---
# Review Bounded Diff
Review only the upstream-base-to-HEAD diff. Compare it with the exact issue,
plan, targeted files, and recorded checks.
Approve only when the change fully implements the requested behavior, stays
inside scope, follows supplied repository guidance, preserves unrelated behavior,
and has a credible verification record. A failed check is acceptable only when
it is recorded as an exception and the diff can still be reviewed against the
issue without claiming that check passed. Reject missing edge behavior,
invented requirements, unsafe input handling, secret exposure, test weakening,
unrelated cleanup, unexplained generated output, or mismatch between plan and
diff.
Do not request stylistic churn or broader redesign. Do not edit code, propose a
new plan or invoke tools. Reject missing or undisclosed checks. Return a forced
structured verdict with short actionable findings. Any finding means rejection.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
