Get the FREE Ultimate OpenClaw Setup Guide →

show

npx machina-cli add skill remenoscodes/claude-git-native-issue/show --openclaw
Files (1)
SKILL.md
894 B

git-native-issue — Show Issue

Show full details and comment history of a specific issue.

Arguments

$ARGUMENTS should be an issue ID (full UUID or abbreviated 4+ char prefix).

If $ARGUMENTS is empty, run git issue ls to show open issues and ask the user which one they want to see.

Steps

  1. Verify prerequisites (git repo, git-issue installed).
  2. Run git issue show <id>.
  3. If the ID is ambiguous (matches multiple issues), display the matches and ask the user to clarify.
  4. If the issue is not found, suggest git issue ls or git issue search "<keyword>".
  5. Display the full output.

Examples

/claude-git-native-issue:show a7f3b2c
/claude-git-native-issue:show                → prompts user to pick an issue

Source

git clone https://github.com/remenoscodes/claude-git-native-issue/blob/main/skills/show/SKILL.mdView on GitHub

Overview

This skill displays full details and the comment history for a specific git-native-issue. You provide an issue ID (full UUID or a 4+ character prefix). If no ID is provided, it lists open issues so you can choose.

How This Skill Works

The skill verifies you’re in a git repo with git-issue installed, then runs git issue show <id>. If the ID matches multiple issues, it lists candidates for selection. If the issue isn’t found, it suggests git issue ls or git issue search <keyword>. The result is the full output of the issue and its comments.

When to Use It

  • When you need the full details and comment history of a specific git-native-issue.
  • When you have an issue ID and want to confirm its content before taking action.
  • When the ID is ambiguous and you need to resolve to a single issue.
  • When you want to locate an issue by keyword via git issue search.
  • When you’re triaging issues and need quick context during a review.

Quick Start

  1. Step 1: Verify prerequisites (git repo, git-issue installed)
  2. Step 2: Run git issue show <id> (or run git issue ls if no ID is provided)
  3. Step 3: If multiple matches appear, select the correct issue or refine your ID

Best Practices

  • Always use a valid ID (full UUID or 4+ character prefix) to avoid ambiguity.
  • If multiple matches appear, review the listed options and pick the correct one.
  • Prefer exact IDs for automation to prevent accidental changes.
  • Ensure you are in the correct git repository before running the command.
  • Cross-check the output against related issues or PRs for context.

Example Use Cases

  • /claude-git-native-issue:show a7f3b2c
  • /claude-git-native-issue:show 550e8400e29b11d4a716446655440000
  • /claude-git-native-issue:show → prompts user to pick an issue
  • /claude-git-native-issue:show 1a2b
  • /claude-git-native-issue:show 1a2b3c4d

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers