القائمة
Code-review finder angle that follows each changed function out to its callers, checking the diff hasn't broken a call-site contract
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Instructions for creating dashboard artifacts with KPI tiles, chart specifications, and breakdown tables from the built-in template
Instructions for creating sortable and filterable data-table artifacts from the built-in template
Instructions for creating explainer artifacts with numbered-step or section walkthrough structures from the built-in template
Instructions for creating long-form report artifacts with a masthead, table of contents, structured sections, and optional appendix from the built-in template
Guided setup and customization workflow for auto mode environment context, optional rule carve-outs, and settings updates
Shared /code-review finder-angle block covering line-by-line diff scanning, removed-behavior auditing, and cross-file tracing
| name | code-review-angle-c-cross-file-tracer |
| description | Code-review finder angle that follows each changed function out to its callers, checking the diff hasn't broken a call-site contract |
| metadata | {"originalName":"Skill: Code Review (Angle C — cross-file tracer)","ccVersion":"2.1.173","sourceUrl":"https://github.com/Piebald-AI/claude-code-system-prompts/blob/main/system-prompts/skill-code-review-angle-c-cross-file-tracer.md","source":{"owner":"Piebald-AI","repo":"claude-code-system-prompts","ref":"main","path":"system-prompts/skill-code-review-angle-c-cross-file-tracer.md"}} |
For each function the diff changes, find its callers (Grep for the symbol) and check whether the change breaks any call site: a new precondition, a changed return shape, a new exception, a timing/ordering dependency. Also check callees: does a parallel change in the same PR make a call unsafe?
