From 609f3c3db02d437222e2c8e171189179d06c3e9c Mon Sep 17 00:00:00 2001 From: DanConwayDev Date: Thu, 5 Mar 2026 13:31:35 +0000 Subject: feat(json): emit nevent1 bech32 IDs in --json output All id and reply_to fields in --json output now use nevent1... bech32 encoding (with relay hint when available) instead of raw hex, making them directly usable as nostr: URI references in --body text. Update SKILL.md to document the nevent1 ID format and enforce use of nostr:nevent1... URIs when cross-referencing events in body text. --- skills/ngit/SKILL.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'skills') diff --git a/skills/ngit/SKILL.md b/skills/ngit/SKILL.md index 7294c82..5c17a70 100644 --- a/skills/ngit/SKILL.md +++ b/skills/ngit/SKILL.md @@ -32,6 +32,8 @@ When you `git fetch`, `git-remote-nostr` reads the current ref state from Nostr - **Use `--offline`** on all but the first `ngit` command in a session — reads from local cache instantly. `git fetch origin` also refreshes the cache. - **Never construct NIP-05 addresses** (`user@domain`). Use the `npub1...` form unless a NIP-05 address was explicitly provided. - **``** accepts a 64-char hex event ID or a `nevent1...` bech32 string. Get IDs from `ngit pr list --json` or `ngit issue list --json`. +- **`--json` output uses `nevent1…` bech32** for all `id` and `reply_to` fields (not raw hex). Use these values directly as `` arguments and in `nostr:` URI references. +- **Reference other issues/PRs/comments in `--body` using `nostr:` URIs** — e.g. `nostr:nevent1abc…` or `nostr:naddr1abc…`. Never paste raw hex IDs into body text. The `id` field from `--json` output is already a valid `nevent1…` string; prefix it with `nostr:` to form the URI. Example: `--body "Relates to nostr:nevent1abc…"`. ngit automatically converts these into the correct event tags. ## Detecting a nostr repo -- cgit v1.2.3