القائمة
Trace impact of a schema or service change across the codebase before modifying
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when bringing the harness method to a NEW or non-sentropic repo — maps the repo's conventions into a harness profile so the same scope/branch/verify kernel applies anywhere.
Use before any creative/design work (a feature, a package, an evolution) — explores intent and design via the spec-ladder with multi-peer adversarial review BEFORE implementation.
Use on any bug, test failure, or unexpected behaviour BEFORE proposing a fix — runs the generic evidence-first root-cause loop.
Use when you have a spec/decisions and need an executable plan — writes a lot-based BRANCH.md from the template and completes with track for realization state.
Use when completing a feature, a design step, or before merging — runs a ≥2-peer consensus review and reconciles the findings, instead of a single rubber-stamp pass.
Use when adding or evolving tests for a feature/bugfix — applies the sentropic test-pyramid, scoped-test loop, environment isolation, and AI-flaky policy.
| name | trace-impact |
| description | Trace impact of a schema or service change across the codebase before modifying |
| paths | api/src/db/schema.ts,api/src/services/** |
| allowed-tools | Read Bash Grep Glob |
grep -r "TABLE_OR_SERVICE" api/src/services/ --include="*.ts" -lgrep -r "TABLE_OR_SERVICE" api/src/routes/ --include="*.ts" -lgrep -r "TABLE_OR_SERVICE" api/tests/ --include="*.ts" -lcontext-* loadersworkspace_id filtering in every query touching this tablespec/DATA_MODEL.md needs sync