fix: disambiguate git-native-issue from Spinellis' git-issue

Both tools register as `git issue` in PATH, so `which git-issue` alone
cannot verify the correct tool is installed. Add a capability probe
(`git issue create --help`) that only passes for git-native-issue
(Spinellis uses `new` instead of `create`).

Updated in setup skill, ambient skill prerequisites, and hook context.

Author: remenoscodes

plugins/claude-git-native-issue/hooks/task-intercept.sh

@@ -9,7 +9,7 @@ cat << 'EOF'
 {
   "hookSpecificOutput": {
     "hookEventName": "UserPromptSubmit",
-    "additionalContext": "git-native-issue is active. For ALL task tracking, use `git issue` commands via Bash instead of internal TaskCreate/TaskUpdate/TaskList tools. Quick reference: create → `git issue create \"title\" -m \"desc\" -l label -p priority`, list → `git issue ls`, show → `git issue show <id>`, progress → `git issue edit <id> --add-label in-progress`, close → `git issue state <id> --close -m \"reason\"`, search → `git issue search \"pattern\"`. AUTONOMOUS BEHAVIOR: (1) Auto-create issues when user starts multi-step work, approves a plan, or discovers a bug. (2) Auto-update with `--add-label in-progress` when starting work, `git issue comment` for progress. (3) Auto-close when task completes successfully. (4) Skip tracking for trivial changes, one-off questions, or when not in a git repo. (5) PLATFORM SYNC: After creating or closing issues, sync with the provider. Detect provider from git remote URL (github.com → github:owner/repo, gitlab.com → gitlab:group/project, gitea/forgejo → gitea:owner/repo). Run `git issue sync <provider>` after mutations. Check `git config --get git-issue.provider` for cached provider string. Before any git-issue command, verify you are in a git repo. If git-issue is not initialized, run `git issue init` first. Invoke the `git-issue-tracker` skill for full reference when needed."
+    "additionalContext": "git-native-issue is active. For ALL task tracking, use `git issue` commands via Bash instead of internal TaskCreate/TaskUpdate/TaskList tools. Quick reference: create → `git issue create \"title\" -m \"desc\" -l label -p priority`, list → `git issue ls`, show → `git issue show <id>`, progress → `git issue edit <id> --add-label in-progress`, close → `git issue state <id> --close -m \"reason\"`, search → `git issue search \"pattern\"`. AUTONOMOUS BEHAVIOR: (1) Auto-create issues when user starts multi-step work, approves a plan, or discovers a bug. (2) Auto-update with `--add-label in-progress` when starting work, `git issue comment` for progress. (3) Auto-close when task completes successfully. (4) Skip tracking for trivial changes, one-off questions, or when not in a git repo. (5) PLATFORM SYNC: After creating or closing issues, sync with the provider. Detect provider from git remote URL (github.com → github:owner/repo, gitlab.com → gitlab:group/project, gitea/forgejo → gitea:owner/repo). Run `git issue sync <provider>` after mutations. Check `git config --get git-issue.provider` for cached provider string. Before any git-issue command, verify you are in a git repo. Then verify the correct tool is installed: run `git issue create --help 2>/dev/null` — if this fails, the wrong `git issue` tool may be installed (Spinellis' git-issue uses `new` instead of `create`). If git-issue is not initialized, run `git issue init` first. Invoke the `git-issue-tracker` skill for full reference when needed."
   }
 }
 EOF

plugins/claude-git-native-issue/skills/git-issue-tracker/SKILL.md

@@ -254,8 +254,9 @@ git issue fsck [--quiet]
 Before running any `git issue` command:
 
 1. **Verify git repo**: `git rev-parse --git-dir 2>/dev/null` — if this fails, you are NOT in a git repo. Do not attempt git-issue operations.
-2. **Verify git-issue installed**: `which git-issue 2>/dev/null` — if missing, tell the user: `brew install remenoscodes/git-native-issue/git-native-issue`
-3. **Check initialization**: `git config --get issue.remote 2>/dev/null` — if not set, run `git issue init` before the first operation. This is a one-time setup per repo.
+2. **Verify git-native-issue installed**: `which git-issue 2>/dev/null` — if missing, tell the user: `brew install remenoscodes/git-native-issue/git-native-issue`
+3. **Verify correct tool**: `git issue create --help 2>/dev/null` — if this fails but step 2 passed, the user has a different `git issue` tool (e.g., Spinellis' git-issue, which uses `new` instead of `create`). Tell the user: "A different `git issue` tool is installed. This plugin requires git-native-issue." Provide: `brew install remenoscodes/git-native-issue/git-native-issue`
+4. **Check initialization**: `git config --get issue.remote 2>/dev/null` — if not set, run `git issue init` before the first operation. This is a one-time setup per repo.
 
 ## Provider Detection
 

plugins/claude-git-native-issue/skills/setup/SKILL.md

@@ -13,17 +13,24 @@ Guide the user through initializing git-native-issue in the current repository a
 ### 1. Check prerequisites
 
 Run these checks in parallel:
-- `which git-issue 2>/dev/null` — verify git-issue is installed
 - `git rev-parse --git-dir 2>/dev/null` — verify we are in a git repo
+- `which git-issue 2>/dev/null` — verify some `git issue` command exists
+- `git issue create --help 2>/dev/null` — verify it is git-native-issue (not Spinellis' git-issue, which uses `new` instead of `create`)
 
-If git-issue is not installed:
+If not in a git repo:
+- Tell the user: "You are not in a git repository. git-native-issue requires a git repo."
+- Stop here.
+
+If no `git-issue` found at all:
 - Tell the user: "git-native-issue is not installed."
 - Provide the install command: `brew install remenoscodes/git-native-issue/git-native-issue`
 - Stop here until installed.
 
-If not in a git repo:
-- Tell the user: "You are not in a git repository. git-native-issue requires a git repo."
-- Stop here.
+If `git-issue` exists but `git issue create --help` fails (wrong tool):
+- Tell the user: "A different `git issue` tool is installed (likely Spinellis' git-issue). This plugin requires git-native-issue."
+- Provide the install command: `brew install remenoscodes/git-native-issue/git-native-issue`
+- Warn: both tools use the `git issue` command — the user may need to adjust PATH priority or uninstall the other tool.
+- Stop here until resolved.
 
 ### 2. Check if already initialized