メニュー
Manage .flake.patches — find fixes for build failures, check if patches landed in nixos-unstable, register or remove patches. Use when a nix build fails after a flake update.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Flake update with fork merge — create merge commit, run flake-lock-merge, advance main. Use when updating flake inputs in a repo with both a public (kdn) and private (fork) remote.
Update flake.lock, handle patches, and test builds. Use when asked to update the flake, run nix run .#update, handle patch failures, or test darwin/nixos builds after an update.
jj version control patterns — working copy, split/squash, bookmarks, fork rebase. Single source of truth for jj usage in this repo; use whenever reaching for a raw git command, or when working with jj commits, splits, rebases, or bookmark management.
SOC 職業分類に基づく
| name | flake-patches |
| description | Manage .flake.patches — find fixes for build failures, check if patches landed in nixos-unstable, register or remove patches. Use when a nix build fails after a flake update. |
| type | Skill |
| timestamp | "2026-07-03T20:19:14.000Z" |
Full reference: docs/flake-patches.md
Patches apply fixes to flake inputs (most commonly nixpkgs) that exist upstream but haven't
landed in the tracked channel (nixos-unstable) yet. Any input with a {name}-upstream
counterpart in flake.nix can be patched.
# 1. Search for fix PRs:
gh search prs "<failing-package>" --repo NixOS/nixpkgs --limit 10
gh search issues "<package> <error>" --repo NixOS/nixpkgs --state open --limit 5
# 2. Get the merge commit of the fix PR:
gh pr view <PR> --repo NixOS/nixpkgs --json mergeCommit --jq '.mergeCommit.oid'
# 3. Check if it's in nixos-unstable yet:
gh api "repos/NixOS/nixpkgs/compare/nixos-unstable...<commit-sha>" --jq '.status'
# "ahead" → not yet landed — register the patch
# "behind" → already landed — no patch needed (or remove existing one)
# "identical" → same commit — already landed
Add to .flake.patches/config.toml:
[patch.nixpkgs.descriptive-name]
url = "https://github.com/NixOS/nixpkgs/pull/<PR>.patch?full_index=1"
# or a specific commit:
[patch.nixpkgs.descriptive-name]
url = "https://github.com/NixOS/nixpkgs/commit/<sha>.patch?full_index=1"
Then apply without re-fetching inputs:
nix run '.#update' -- g:patches
When a patch has landed in the tracked channel:
[patch.<input>.<name>] entry in .flake.patches/config.toml.patch file under .flake.patches/<input>/nix run '.#update' -- g:patchesstaging-next is a long-running branch that accumulates large/destructive changes before
merging to master. Fixes there take weeks to reach nixos-unstable — don't register patches
from staging-next PRs unless you're prepared to carry them for a long time.