Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
aqe-test-change - Skill - OpenSmartRoute
Skillv1.0.0
aqe-test-change
Design, implement, and run durable tests for Agentic QE code changes. Use when adding tests, reproducing a defect, filling a coverage gap, selecting affected Vitest suites, checking CLI/MCP parity…
Imported from proffesor-for-testing/agentic-qe (.agents/skills/aqe-test-change/SKILL.md). Install upstream with npx skills add proffesor-for-testing/agentic-qe --skill aqe-test-change. Copyright stays with the author.
Test an AQE Change
Read AGENTS.md, the changed code, nearby tests, and relevant public
interfaces.
Reproduce a reported defect with the exact scenario before changing code.
durable boundary contracts, invariants, or properties;
integration behavior across affected components;
focused unit examples needed for the red-green loop.
Keep tests deterministic. Do not hide failures with retries, skips, weakened
assertions, fabricated fixtures, or mocks of the behavior under test.
Run the narrowest matching Vitest target first. Expand to typecheck, build,
agent/skill parity, MCP integration, or full CI checks in proportion to the
changed surface.
For capabilities exposed through both CLI and MCP, verify both paths.
Report commands, pass/fail counts, limitations, and untested external
dependencies.
Never modify or reset .agentic-qe/memory.db. Use a copy for any database test.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install aqe-test-change and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
{
"ocm": "1",
"id": "proffesor-for-testing-agentic-qe-aqe-test-change",
"kind": "skill",
"name": "aqe-test-change",
"description": "Design, implement, and run durable tests for Agentic QE code changes. Use when adding tests, reproducing a defect, filling a coverage gap, selecting affected Vitest suites, checking CLI/MCP parity, or verifying a fix in this repository. Do not use for a read-only quality review with no requested edits.",
"publisher": "proffesor-for-testing",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Design, implement, and run durable tests for Agentic QE code changes. Use when adding tests, reproducing a defect, filling a coverage gap, selecting affected Vitest suites, checking CLI/MCP parity, or verifying a fix in this repository. Do not use for a read-only quality review with no requested edits."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/proffesor-for-testing/agentic-qe",
"path": ".agents/skills/aqe-test-change/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/proffesor-for-testing/agentic-qe/blob/HEAD/.agents/skills/aqe-test-change/SKILL.md",
"key": "proffesor-for-testing/agentic-qe/.agents/skills/aqe-test-change/SKILL.md"
}
},
"instructions": "# Test an AQE Change\n\n1. Read `AGENTS.md`, the changed code, nearby tests, and relevant public\n interfaces.\n2. Reproduce a reported defect with the exact scenario before changing code.\n3. Identify the affected QE specialty from\n [references/test-specialties.md](references/test-specialties.md).\n4. Add tests in this order:\n - durable boundary contracts, invariants, or properties;\n - integration behavior across affected components;\n - focused unit examples needed for the red-green loop.\n5. Keep tests deterministic. Do not hide failures with retries, skips, weakened\n assertions, fabricated fixtures, or mocks of the behavior under test.\n6. Run the narrowest matching Vitest target first. Expand to typecheck, build,\n agent/skill parity, MCP integration, or full CI checks in proportion to the\n changed surface.\n7. For capabilities exposed through both CLI and MCP, verify both paths.\n8. Report commands, pass/fail counts, limitations, and untested external\n dependencies.\n\nNever modify or reset `.agentic-qe/memory.db`. Use a copy for any database test.",
"cost": {
"context_tokens": 268
}
}
Fetch it by URL: GET /api/v1/registry/proffesor-for-testing-agentic-qe-aqe-test-change/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.