HighlightsHighlights

• Nostr-signed Git commits — same workflow as GPG from Git’s perspective: git commit -S, git verify-commit, git log --show-signature (gpg.program + openpgp).
• Keys — nsec (or hex) on disk, or Amber via NIP-46 (approve each sign on the phone).
• Install & upgrades — signed releases on relays + Blossom (hash + publisher key); curl …/install.sh then local npm/pnpm -g; git-nostr-update --check for updates.
• Setup — git-nostr-setup once (wizard); -N + flags / GNS_* for CI or headless (non-interactive path: v0.3.0).
• Operational CLIs — git-nostr-sign config-git (reapply Git signing from saved config), doctor / status (sanity check), check-pages (hosted nostr.json / install.sh vs identity.json) (v0.4.0).
• Optional hosting — wizard can deploy Codeberg Pages so your NIP-05 and install.sh share one HTTPS origin (skip if you only want local signing).

curl -fsSL https://nostr-svrn.codeberg.page/install.sh | sh
git-nostr-setup   # first time only

Typical dayTypical day

git add -p
git commit -S -m "fix: handle empty relay list"
git verify-commit HEAD
# git log -1 --show-signature

With Amber, you get a prompt on the device when git invokes the signer — same idea for tags (git tag -s if you use signed tags).

Posting v0.4.1 — better author hints when Amber’s signing key isn’t your publisher NIP-05; landing page shows the shipped semver + common commands; default relays for updates refreshed.

On NostrOn Nostr

npub1…qkzc2 · git-nostr-sign@nostr-svrn.codeberg.page · kind 1063 (releases) & kind 1 (ship notes).

Node 18+, MIT. Feedback welcome (installer edge cases, Amber UX, distribution).