test-plan
A filled-in example of the test plan this agent produces before writing code. Copy the shape for any new behavior: enumerate cases by type, mark scope, and state how to run + gate.
$ npx -y skills add vanara-agents/skills --agent claude-codeHow it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
A filled-in example of the test plan this agent produces before writing code. Copy the shape for any new behavior: enumerate cases by type, mark scope, and state how to run + gate.
Agent definition
test-plan.mdTest Plan: Refund Eligibility
A filled-in example of the test plan this agent produces before writing code. Copy the shape for any new behavior: enumerate cases by type, mark scope, and state how to run + gate.
Behavior under test
`isRefundEligible(order, now)` decides whether an order can be refunded. An order is eligible when it was placed within the last 30 days, is unused, and has not already been refunded.
Cases
| # | Case | Type | Expected | |---|---|---|---| | 1 | order placed 5 days ago, unused | happy | `true` | | 2 | order placed exactly 30 days ago | boundary | `true` (inclusive) | | 3 | order placed 31 days ago | boundary | `false` | | 4 | order placed 0 days ago (today) | boundary | `true` | | 5 | order already marked refunded | failure | throws `AlreadyRefunded` | | 6 | order is `null` / missing | failure | throws `NotFound` | | 7 | order used (redeemed) | edge | `false` |
Determinism notes
- `now` is **injected**, not read from the system clock, so the 30-day boundary tests are
stable. The suite freezes `now` to `2026-06-29T12:00:00Z`.
- No network or DB access — `order` is built by a `makeOrder(overrides)` factory.
Out of scope (tracked separately)
- Partial refunds and refund *amount* calculation — separate behavior, separate plan.
- Payment-provider interaction — covered by an integration test, not this unit.
Coverage target
80% minimum (branch coverage emphasized — every `true`/`false`/throw path above is exercised).
How to run
# Run just this behavior's tests
npm test -- refund
# Gate coverage in CI (fails below 80%)
node scripts/check-coverage.mjs coverage/coverage-summary.json --min=80
Red → Green evidence (to be filled at implementation time)
RED: 5 failing — isRefundEligible is not defined
GREEN: 7 passing — statements 92% · branches 88% · target 80% met
Gaps: none for this behavior; partial-refund path intentionally deferred
Read more
Test Plan: Refund Eligibility
A filled-in example of the test plan this agent produces before writing code. Copy the shape for any new behavior: enumerate cases by type, mark scope, and state how to run + gate.
Behavior under test
`isRefundEligible(order, now)` decides whether an order can be refunded. An order is eligible when it was placed within the last 30 days, is unused, and has not already been refunded.
Cases
| # | Case | Type | Expected | |---|---|---|---| | 1 | order placed 5 days ago, unused | happy | `true` | | 2 | order placed exactly 30 days ago | boundary | `true` (inclusive) | | 3 | order placed 31 days ago | boundary | `false` | | 4 | order placed 0 days ago (today) | boundary | `true` | | 5 | order already marked refunded | failure | throws `AlreadyRefunded` | | 6 | order is `null` / missing | failure | throws `NotFound` | | 7 | order used (redeemed) | edge | `false` |
Determinism notes
- `now` is **injected**, not read from the system clock, so the 30-day boundary tests are
stable. The suite freezes `now` to `2026-06-29T12:00:00Z`.
- No network or DB access — `order` is built by a `makeOrder(overrides)` factory.
Out of scope (tracked separately)
- Partial refunds and refund *amount* calculation — separate behavior, separate plan.
- Payment-provider interaction — covered by an integration test, not this unit.
Coverage target
80% minimum (branch coverage emphasized — every `true`/`false`/throw path above is exercised).
How to run
# Run just this behavior's tests npm test -- refund # Gate coverage in CI (fails below 80%) node scripts/check-coverage.mjs coverage/coverage-summary.json --min=80
Red → Green evidence (to be filled at implementation time)
RED: 5 failing — isRefundEligible is not defined GREEN: 7 passing — statements 92% · branches 88% · target 80% met Gaps: none for this behavior; partial-refund path intentionally deferred
🐒 Free agents, skills & packs for Claude Code One subscription. An army of Claude Code agents. 30 production-grade agents, skills, and packs for Claude Code — free, Apache-2.0, install with one command.
Repo: vanara-agents/skills
Other agents on vanara-agents-skills.
- AGENT
Use when designing a new HTTP/GraphQL API or changing an existing one — modeling resources, defining endpoint contracts, choosing status codes, pagination, filtering, error envelopes, versioning, and idempotency. Produces a reviewable API contract plus an OpenAPI snippet, not
Open agent - review-notes
This shows how the api-designer agent reviews a flawed draft. Findings are severity-ranked so the implementer fixes the contract-breakers first. Severity legend: **CRITICAL** (breaks clients / data risk), **HIGH** (real bug or inconsistency), **MEDIUM** (maintainability),
Open agent - contract-and-openapi
The contract is the deliverable. Express it as an **OpenAPI 3.1** document so it is human-readable *and* machine-checkable. This reference covers how to structure that document and what `scripts/lint-openapi.mjs` enforces.
Open agent - design-checklist
Run through this before declaring an API contract done. It is ordered the way you should *design*: resources first, cross-cutting rules last. Every box is a place real APIs go wrong in production.
Open agent - versioning-and-evolution
APIs are forever once published: a consumer you've never met may depend on any field you expose. Design so you can **add without breaking**, and version explicitly when you must break.
Open agent - pr-comment-template
Copy-paste templates for leaving review comments. Keep each comment to one finding: an anchor, the problem, and the fix.
Open agent