stevesolun/ctx / .claude/skills/ctx-verify
ctx-verify
VerifiedSelect 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 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |