Name: release-check
Author: work-w-chrstnrpj

Imported from work-w-chrstnrpj/Notable_Finance (.github/skills/release-check/SKILL.md). Install upstream with npx skills add work-w-chrstnrpj/Notable_Finance --skill release-check. Copyright stays with the author.

Release Check

Workflow

Confirm scope and unresolved work.
Review relevant lint, typecheck, test, build, and e2e commands from project docs.
Check docs, changelog, environment variables, deployment notes, and generated files.
Confirm no secrets, large generated outputs, or unrelated local files are included.
Summarize verification results and known risks.

Boundaries

Do not deploy to production without approval.
Do not claim checks passed unless they ran or were reviewed from reliable output.
Do not include generated graph or snapshot outputs unless intentionally reviewed.

Output

Relevant files or docs inspected.
Work completed or plan produced.
Tests or verification run or recommended.
Docs updated or skipped with reason.
Remaining risks, assumptions, and handoffs.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -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}'

Install release-check 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": "work-w-chrstnrpj-notable-finance-release-check", "kind": "skill", "name": "release-check", "description": "Prepare code for merge or release with verification, docs, environment, and deployment checks.", "publisher": "work-w-chrstnrpj", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Prepare code for merge or release with verification, docs, environment, and deployment checks." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/work-w-chrstnrpj/Notable_Finance", "path": ".github/skills/release-check/SKILL.md", "ref": "28c8d1b2a5159ab4c59a97c45958db5d0b537489", "url": "https://github.com/work-w-chrstnrpj/Notable_Finance/blob/28c8d1b2a5159ab4c59a97c45958db5d0b537489/.github/skills/release-check/SKILL.md", "key": "work-w-chrstnrpj/Notable_Finance/.github/skills/release-check/SKILL.md" } }, "instructions": "# Release Check\n\n## Workflow\n\n1. Confirm scope and unresolved work.\n2. Review relevant lint, typecheck, test, build, and e2e commands from project docs.\n3. Check docs, changelog, environment variables, deployment notes, and generated files.\n4. Confirm no secrets, large generated outputs, or unrelated local files are included.\n5. Summarize verification results and known risks.\n\n## Boundaries\n\n- Do not deploy to production without approval.\n- Do not claim checks passed unless they ran or were reviewed from reliable output.\n- Do not include generated graph or snapshot outputs unless intentionally", "cost": { "context_tokens": 205 } }

release-check

About

Release Check

Workflow

Boundaries

Output

Use it

Install release-check and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews