القائمة
Run before modifying a function — impact + test-map + explain in one pass, presented as a modification checklist.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run a multi-category code audit on the cqs codebase. Spawns parallel agents per batch.
Trust-boundary security audit of cqs — fans out unbiddable-auditor agents across 6 categories (RT-INJ/RT-FS/RT-RES/RT-DATA/RT-RELAY/RT-EXFIL), attacker mindset, run-the-attack PoC + regression guard.
Run the retrieval recall gate with dead-gold triage and the binary A/B regression test. Required before release tags; use after any retrieval-adjacent merge.
Run after making changes, before committing — reviews the current git diff for impact and risk via cqs review.
Release a new version of cqs. Bumps version, updates changelog, runs the recall gate, publishes to crates.io, creates GitHub release.
One-command setup for cqs in a new project — skills, tears infrastructure, CLAUDE.md, init, index.
| name | before-edit |
| description | Run before modifying a function — impact + test-map + explain in one pass, presented as a modification checklist. |
| argument-hint | <function_name> |
Run before modifying any function. Shows what breaks, what tests cover it, and what to check.
<function_name> — the function you're about to editcqs impact <function_name> --json via Bashcqs test-map <function_name> --json via Bashcqs explain <function_name> --json via BashPresent this to the user (fill in from the JSON results):
## Impact Analysis: <function_name>
**Signature:** <from explain>
**File:** <from explain>
**Callers (<count>):** <list top 10 caller names with files>
**Tests (<count>):** <list test names>
**Risk:** <High if >10 callers, Medium if 3-10, Low if 0-2>
### Before you edit:
- [ ] Understand what callers expect (check the top callers above)
- [ ] Note the existing tests — run them after your change
- [ ] If changing the signature or return type, update all callers
### After you edit:
- [ ] Run: `cargo test --features cuda-index -- <test_names>`
- [ ] If tests fail, check whether your change broke the caller contract
- [ ] If no tests cover the changed behavior, write one
cqs impact returns empty results, the function may be dead code or a leaf node — note thiscqs test-map returns empty, flag as "NO TESTS — write tests before and after editing"cqs explain fails (function not indexed), fall back to cqs "<function_name>" --name-only --json