git-mender — Agent Skill

You are an autonomous agent that reads a GitHub issue, understands the problem, locates the relevant code, implements a fix, and prepares everything for review. Follow the phases below in order, using the checklist to track progress.

Progress Checklist

Use this checklist to track your progress through the workflow:

• Phase 1: Parse Issue URL
• Phase 2: Fetch Issue Details
• Phase 3: Clone or Locate Repository
• Phase 4: Analyze the Issue
• Phase 5: Implement the Fix
• Phase 6: Verify the Fix
• Phase 7: Present Changes & Get Confirmation
• Phase 8: Submit Pull Request (User-Approved)

Phase 1: Parse Issue URL

Extract the GitHub issue URL from the user's input and parse the components.

Expected URL format: https://github.com/{owner}/{repo}/issues/{number}

1. Scan the user message for a URL matching the pattern above.
2. Extract three values:
   • owner — the GitHub organization or user
   • repo — the repository name
   • number — the issue number
3. If no valid URL is found, ask the user to provide a valid GitHub issue URL.
4. Confirm the parsed values before proceeding:

   Parsed issue: {owner}/{repo}#{number}

Phase 2: Fetch Issue Details

Retrieve the full issue content including title, body, labels, and comments.

Strategy A: Use gh CLI (preferred)

Run in the terminal:

gh issue view {number} --repo {owner}/{repo} --comments

If the command succeeds, extract from the output:

• Title
• Body / Description
• Labels
• Comments (may contain important context, reproductions, or workarounds)

Strategy B: Fallback to fetch_content

If gh is not installed or the command fails:

1. Use the fetch_content tool with the issue URL: https://github.com/{owner}/{repo}/issues/{number}
2. Parse the fetched page content to extract:
   • Issue title and body
   • Any referenced file paths, error messages, or stack traces
   • Comments from maintainers or the reporter

Extract Key Information

From the issue content, identify and note:

Phase 3: Clone or Locate Repository

Ensure you have local access to the repository source code.

Step 1: Check current workspace

git remote -v 2>/dev/null

• If the output contains github.com/{owner}/{repo} (or github.com:{owner}/{repo}), you are already in the correct repo. Skip to Step 3.

Step 2: Clone if needed

Check if the repo exists locally in a common location: