skills.rest
mkusaka
mkusakaCOMMUNITY
Explore all skills by this author →
GitHub

code-review-angle-c-cross-file-tracer

Trace changed functions to callers and validate call-site contracts from diff files.

7|Updated Mar 8, 2026
Search Tags:#code quality#diff analysis#code review#call-site contract#function tracing
One-click install
npx skills add https://github.com/mkusaka/ccskills --skill code-review-angle-c-cross-file-tracer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-angle-c-cross-file-tracer
Source: https://github.com/mkusaka/ccskills/tree/main/skills/code-review-angle-c-cross-file-tracer
Command: npx skills add https://github.com/mkusaka/ccskills --skill code-review-angle-c-cross-file-tracer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies changes to functions in code, traces these changes to their callers, and checks if the changes have broken any call-site contracts.

Core Features & Use Cases

  • Function Change Tracing: Follows each changed function to its callers.
  • Call-Site Contract Validation: Checks for preconditions, return shapes, and exception changes.
  • Callee Safety Check: Ensures that changes in parallel PRs do not make calls unsafe.
  • Use Case: When you've made changes to a function, use this Skill to validate that these changes haven't negatively impacted other parts of your codebase.

Quick Start

Analyze the changes in the 'function-changes.diff' to ensure no call-site contracts are broken.

Frequently Asked Questions about code-review-angle-c-cross-file-tracer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace changed functions to their callers during code review?▼

Tracing changed functions to their callers during code review is done by analyzing diff files and comparing them with source code. This identifies callers and validates that modifications do not break existing call-site contracts.

What is a call-site contract and how do I validate it after modifying a function?▼

A call-site contract defines the preconditions, return shapes, and exceptions expected by a function's callers. Validating it requires analyzing function changes and checking all call sites to ensure modifications have not broken these expectations.

How do I check if parallel pull requests have made function calls unsafe?▼

Checking if parallel pull requests have made function calls unsafe is done by performing a callee safety check. This analyzes concurrent changes to ensure modifications in parallel PRs do not break existing function contracts.

Can I analyze diff files to detect broken preconditions and return shapes automatically?▼

Yes, you can analyze diff files to detect broken preconditions and return shapes automatically. The tool compares function changes against source code to validate call-site contracts and identify any impacted callers.

What's the best way to validate codebase safety when changing shared functions?▼

The best way to validate codebase safety when changing shared functions is to trace each change to its callers. This checks preconditions, return shapes, and exceptions to ensure modifications do not negatively impact other parts of the repository.

Related Skills

Explore More Software Engineering Skills→
aio-libsaio-libs
1.4k

check-override-drift

Analyze aiobotocore PR diffs for drift against botocore source code.

Official
Advanced
Terry-MaoTerry-Mao
144

security-review-pr

Audit pull request diffs for security concerns and integrate findings into review.json.

Community
Advanced
jikig-aijikig-ai
12

semgrep-sast

Scan git-diff-selected source files with semgrep for vulnerability patterns.

Official
Intermediate
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic