What problem does it solve? Bumping Nix flake inputs can silently break a configuration when upstream renames options, deprecates APIs, or changes behavior. This Skill inspects an uncommitted flake.lock bump before you switch, so you know exactly what changed and whether your repo is affected. ## Core Features & Use Cases - Lock diffing: Compares old and new flake.lock revisions for watched structural inputs like den, flake-parts, home-manager, nix-darwin, sops-nix, and nixpkgs. - Upstream analysis: Prefetches both revisions into the Nix store, diffs the source trees, and reads upstream commit messages via the GitHub API for breaking-change markers. - Repo intersection: Searches src/modules for call sites of changed symbols, so only changes that actually affect your code are reported with file:line citations. - Use Case: After running just update, invoke the skill headlessly to get a verdict (safe / needs attention / blocking) plus likely breakages, obsoleted workarounds, and doc actions before switching generations. ## Quick Start Run the flake-brief skill to analyze my uncommitted flake.lock bump and give me the transition brief.