api regression guard
- Repo stars 1
- Author repo claude-skills
- Domain
- Engineering
- 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.
# API Regression Guard
## Overview
Check whether code changes silently broke API contracts, behavior, schemas, or compatibility expectations.
## Core Workflow
1. Inspect the relevant diffs, configs, source files, or artifacts before forming a conclusion.
2. Compare the current state against repo conventions, expected guarantees, and known risk areas.
3. Prioritize the highest-impact gaps, regressions, or improvement opportunities instead of surface-level noise.
4. Recommend the smallest high-leverage changes and the checks that would validate them.
## Deliver
- Ranked findings or improvement opportunities with clear evidence.
- The main risks, tradeoffs, or regressions that matter most.
- Validation steps or follow-up edits that would reduce risk.
## Guardrails
- Lead with findings, not generic praise or low-value commentary.
- Use repo evidence and surrounding context instead of reviewing in isolation.
- Flag missing validation when a recommendation depends on behavior you could not confirm.
- Prefer repository evidence, command output, and nearby tests over vague intuition.
Sections and files
Listed in source order.
sections -> Overview → Core Workflow → Deliver → Guardrails
terms -> Check whether code changes silently broke API contracts, behavior, schemas, or compatibility expectations. · 1. Inspect the relevant diffs, configs, source files, or artifacts before forming a conclusion. · - Ranked findings or improvement opportunities with clear evidence. · - Lead with findings, not generic praise or low-value commentary.
files/cmd -> no explicit files or commands
body sha256 -> d1e55b5d232f
Core Workflow
Inspect the relevant diffs, configs, source files, or artifacts before forming a conclusion. Compare the current state against repo conventions, expected guarantees, and known risk areas. Prioritize the highest-impact gaps, regressions, or improvement opportunities instead of surface-level noise. Recommend the smallest high-leverage changes and the checks that would validate them.
Deliver
Ranked findings or improvement opportunities with clear evidence. The main risks, tradeoffs, or regressions that matter most. Validation steps or follow-up edits that would reduce risk.
Guardrails
Lead with findings, not generic praise or low-value commentary. Use repo evidence and surrounding context instead of reviewing in isolation. Flag missing validation when a recommendation depends on behavior you could not confirm. Prefer repository evidence, command output, and nearby tests over vague intuition.