name	regression-risk-review
description	Regression-risk review for behavior changes likely to break existing users, flows, integrations, or production data.
license	MIT

Regression-risk review for behavior changes likely to break existing users, flows, integrations, or production data.

Inspect changed files and diff hunks relevant to this skill.
Use repository-native tools when available.
Prefer exact evidence from changed code.
Emit findings using the shared JSONL finding contract.
Avoid style-only comments unless they create maintainability or correctness risk.

Use grep or editor search before opening files.
Use git, grep, and gh CLI. These are universally available and sufficient for all review tasks.
Do not depend on tools beyond git, grep, cat, head, wc, and gh.

Más de este repositorio

mismo repositorio

Resolve GitHub PR review comments safely, read unresolved comments, validate each issue, make minimal fixes, test, commit, and resolve.

Use zero-install context minimization first, with optional local optimization tooling when available.

Accessibility review for semantic HTML, ARIA, keyboard support, focus, screen readers, contrast, and WCAG-oriented issues.

API and contract review for OpenAPI/AsyncAPI/protobuf changes, backwards compatibility, schemas, status codes, and examples.

Architecture review for SOLID, layering, boundaries, coupling, cohesion, extensibility, and maintainability.

Backend review for handlers, services, validation, errors, transactions, dependency boundaries, and service contracts.

name	regression-risk-review
description	Regression-risk review for behavior changes likely to break existing users, flows, integrations, or production data.
license	MIT

Regression-risk review for behavior changes likely to break existing users, flows, integrations, or production data.

Inspect changed files and diff hunks relevant to this skill.
Use repository-native tools when available.
Prefer exact evidence from changed code.
Emit findings using the shared JSONL finding contract.
Avoid style-only comments unless they create maintainability or correctness risk.

Use grep or editor search before opening files.
Use git, grep, and gh CLI. These are universally available and sufficient for all review tasks.
Do not depend on tools beyond git, grep, cat, head, wc, and gh.