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.
- License 许可
- MIT
- 所属仓库
- stevesolun/ctx
- 最近更新
- 2026-10-15
- Stars
- ★ 593
- Forks
- 69
01 前言 Front Matter
- name
- ctx-verify
- description
- 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.
03 SKILL.md 正文
Verify ctx changes
- Inspect the requested behavior and changed surface. Read only the relevant
section of
CONTRIBUTING.mdbefore 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.
04 同仓库更多 Skills
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing toolboxes with a team.
skill-router
Alive skill router — reads the current project's stack and loads/unloads skills dynamically. Invoke at session start or when project context changes.
repo-stats-autoupdate
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
find-skills
Discover installable agent skills from ctx's shipped Skills.sh catalog, the Skills.sh search API, and the npx skills CLI. Use when a user asks whether a skill exists, wants to add/update a skill, or needs a repeatable procedure for finding candidate skills safely.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.