Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Verify ctx changes

  1. 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.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Create or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules. Use when a repo lacks durable agent guidance or when a custom harness needs a predictable context file.

The English summary is being prepared. Showing the original description.

stevesolun/ctx588Updated Oct 15, 2026

Recommend the smallest Matt Pocock skill or short skill sequence that fits the user's current goal.

The English summary is being prepared. Showing the original description.

stevesolun/ctx588Updated Oct 15, 2026

Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", "save context", "compressed agent output".

The English summary is being prepared. Showing the original description.

stevesolun/ctx588Updated Oct 15, 2026

Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.

The English summary is being prepared. Showing the original description.

stevesolun/ctx588Updated Oct 15, 2026

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

The English summary is being prepared. Showing the original description.

stevesolun/ctx588Updated Oct 15, 2026

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

The English summary is being prepared. Showing the original description.

stevesolun/ctx588Updated Oct 15, 2026

See all skills by stevesolun

Report a problem with this skill