How do I install the Ctx Verify skill?

Run npx skillmds@latest add stevesolun/ctx-verify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ctx Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ctx Verify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ctx Verify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ctx Verify?

stevesolun (@stevesolun) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ctx Verify by stevesolun — Agent Skill

Name: Ctx Verify
Author: stevesolun

Ctx Verify

Select proportional validation for changes or reviews in the ctx repository. Use before handing off material code, workflow, migration, documentation, security, packaging, or release changes; before a PR; or when asked whether a change is adequately tested. Do not use for pure questions with no changed artifact.

stevesolun ec0aa1e 2.6 KB Updated Sep 17, 2026

File contents

Verify ctx changes

Inspect the requested behavior and changed surface. Read only the relevant section of CONTRIBUTING.md before selecting checks.
Run the smallest focused tests or deterministic checks that exercise the changed behavior first.
Escalate evidence in proportion to risk:
- Small, localized change: focused tests, schemas, or diff checks.
- Material repository change: scripts/no_mistakes_run.sh fast.
- PR-level, contract, workflow, migration, packaging, security, or release change: run the fast gate, then python scripts/ci_preflight.py --profile pr.
- Documentation navigation or linked public-asset change: follow the tracker contract in CONTRIBUTING.md; do not require tracker changes for ordinary prose-only edits.
- Windows-sensitive change: follow the native-CI contract in CONTRIBUTING.md; local checks do not replace required Windows evidence.
Treat the fast gate as committed-history evidence. When the working tree is dirty, pair it with focused checks against the actual uncommitted changes.
If a gate cannot find its trusted pytest, Ruff, and mypy environment, report the environment failure. Do not silently install dependencies or weaken the trust check.
Use an independent validator only when semantic risk remains after deterministic checks, especially for material security, migration, or release work.
Report each check, its result, and any omitted or unavailable evidence.

Rubric

Mark each applicable criterion pass, fail, or not verified:

Intent: The artifact satisfies the request without unrelated scope.
Behavior: Fresh evidence covers the changed success path and relevant failure or regression paths.
Static integrity: Applicable lint, formatting, and type checks pass.
Repository contracts: Migration, changed-file, documentation, packaging, and platform requirements remain satisfied where relevant.
Evidence quality: Results apply to the actual changed surface and are not stale or inapplicable.
Handoff: Skipped checks and residual risks are stated plainly.

Do not claim completion while an applicable criterion fails. Treat missing required evidence as not verified, not as a pass.

---name: ctx-verifydescription: Select proportional validation for changes or reviews in the ctx repository. Use before handing off material code, workflow, migration, documentation, security, packaging, or release changes; before a PR; or when asked whether a change is adequately tested. Do not use for pure questions with no changed artifact.---# Verify ctx changes1. Inspect the requested behavior and changed surface. Read only the relevant section of `CONTRIBUTING.md` before selecting checks.2. Run the smallest focused tests or deterministic checks that exercise the changed behavior first.3. Escalate evidence in proportion to risk: - Small, localized change: focused tests, schemas, or diff checks. - Material repository change: `scripts/no_mistakes_run.sh fast`. - PR-level, contract, workflow, migration, packaging, security, or release change: run the fast gate, then `python scripts/ci_preflight.py --profile pr`. - Documentation navigation or linked public-asset change: follow the tracker contract in `CONTRIBUTING.md`; do not require tracker changes for ordinary prose-only edits. - Windows-sensitive change: follow the native-CI contract in `CONTRIBUTING.md`; local checks do not replace required Windows evidence.4. Treat the fast gate as committed-history evidence. When the working tree is dirty, pair it with focused checks against the actual uncommitted changes.5. If a gate cannot find its trusted pytest, Ruff, and mypy environment, report the environment failure. Do not silently install dependencies or weaken the trust check.6. Use an independent validator only when semantic risk remains after deterministic checks, especially for material security, migration, or release work.7. Report each check, its result, and any omitted or unavailable evidence.## RubricMark each applicable criterion `pass`, `fail`, or `not verified`:- **Intent:** The artifact satisfies the request without unrelated scope.- **Behavior:** Fresh evidence covers the changed success path and relevant failure or regression paths.- **Static integrity:** Applicable lint, formatting, and type checks pass.- **Repository contracts:** Migration, changed-file, documentation, packaging, and platform requirements remain satisfied where relevant.- **Evidence quality:** Results apply to the actual changed surface and are not stale or inapplicable.- **Handoff:** Skipped checks and residual risks are stated plainly.Do not claim completion while an applicable criterion fails. Treat missingrequired evidence as `not verified`, not as a pass.

Frequently asked questions