Generate a structured chip migration diff report from evidence about old and new chips. Use when the user needs a grounded report of register, interface, DeviceTree, binding, code impact, risk, and manual-confirmation differences before patching or testing.
Use this skill to turn raw evidence into a structured migration diff report.
The goal is not to describe every change. The goal is to isolate changes that affect software behavior and can drive patching, review, and testing.
chip-rag-evidence, or equivalent local materialGroup changes by software impact domain. Suggested domains:
Classify each difference. Use one of:
Map each difference to impact. For each item include:
Separate facts from inference.
Evidence-backed facts stay in the main report.
Inferred impact goes under needs verification.
Return results in this shape:
Chip Migration Diff Report
- Scope:
- Source:
- Target:
Diff Items
- [high] change type | shared or version-specific | evidence ids | affected area | recommended validation
Needs Verification
- item | why unresolved
Manual Checks
- hardware fact to confirm