backend-test

Verify changed backend routes with targeted HTTP requests against the actual diff.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/guneysol/agent-configs --skill backend-test-guneysol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-test
Source: https://github.com/guneysol/agent-configs/tree/main/agents/skills/backend-test
Command: npx skills add https://github.com/guneysol/agent-configs --skill backend-test-guneysol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews and unit tests often miss whether a changed backend route actually behaves correctly at runtime. This Skill verifies modified routes and handlers by sending targeted HTTP requests against a live service, confirming status codes, response shapes, validation, and edge cases tied directly to the diff. ## Core Features & Use Cases - Diff-Driven Test Design: Inspects the actual code diff first, then designs requests that exercise exactly the changed behavior rather than generic happy-path checks. - Safe Live Verification: Reuses a healthy running server when available, or starts the service with isolated ports and temporary data stores, never touching production data. - Structured Pass/Fail Reporting: Reports what changed, the request used, expected versus actual results, and a clear pass or fail verdict for each behavior change. - Use Case: After modifying an endpoint's query parameter validation, ask the agent to verify the route; it will start the local service if needed, send targeted curl requests covering valid and invalid inputs, and report exactly which checks passed or failed. ## Quick Start Verify the backend routes I just changed by running targeted requests against the local service and report pass or fail for each behavior change.

Frequently Asked Questions about backend-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test changed backend API routes after editing code?▼

Inspect the diff to identify changed behavior, then send targeted HTTP requests with curl covering the modified code paths. Verify status codes, response shape, validation, and edge cases, and report expected versus actual results for each change.

How to test an API endpoint that requires a JWT token?▼

Pass the token in an Authorization: Bearer header only when the user supplied it for the test. If no usable token is available, skip only the auth-blocked checks and clearly state which verifications were blocked.

Can I run backend route tests without a running server?▼

Yes, the service can be started locally using the repository's own command, with isolated ports and temporary data stores. In a worktree, required env files are copied from the main checkout without printing their contents.

Is it safe to run API tests against production data?▼

No, adversarial or edge-case tests must never target production data. Use isolated ports and temporary data stores for local dependencies, and record every started process so only those are stopped afterward.

What should a backend route test report include?▼

Each behavior change should report what changed, the exact request used, the expected result, the actual result, and a pass or fail verdict. Failures should explain the mismatch and point to the likely code path.