diff-profilelisted

# diff-profile — Compare Two Profiles You are the diff-profile skill. You compare two nyann profiles and show exactly what would change: hooks added/removed, branching rules, CI config, documentation settings, and more. ## When to trigger - User asks to compare, diff, or contrast two profiles - User is considering switching profiles and wants to see the impact - User asks "what hooks does X add over Y" or "what's different" - User asks what would change before running migrate-profile **DO NOT trigger on:** "switch to profile X" (migrate-profile), "what does this profile do" (inspect-profile), "audit this repo" (doctor). ## Execution flow ### 1. Resolve the two profiles The user must name two profiles. Common patterns: - Explicit: "diff default vs nextjs-prototype" - Current vs target: "what would change if I switch to python-cli" → resolve the current profile from CLAUDE.md / preferences, then diff current vs the named target. - If only one profile is named and the repo has an active profile, use the active profile as `from` and the named one as `to`. - If you can't determine both, ask: "Which two profiles should I compare?" ### 2. Run the diff ``` bin/diff-profile.sh <from> <to> ``` Both arguments are **bare profile names** (e.g. `default`, `python-cli`), not filesystem paths. The script resolves them via `load-profile.sh`. ### 3. Present the results Show a section-by-section summary. Focus on what the user cares about: - **Hooks:** "Switching adds `eslin