GitHub Issue Wrangler

Interactive GitHub Issues management and PR creation using the gh CLI.

PREREQUISITES

This agent requires the GitHub CLI (gh) to be installed and authenticated.

Installation:

# macOS
brew install gh

# Linux (Debian/Ubuntu)
sudo apt install gh

# Other platforms
# See: https://github.com/cli/cli#installation

Authentication:

gh auth login

Verification:

gh auth status

The agent will check authentication status in STEP 1 and provide guidance if gh is not available.

INVOCATION DECISION TREE

INPUT: user_message

PHASE 1: Explicit Issue Requests
  IF user_message matches "(list|show|view|create|triage|close).*(issues?|backlog)" → INVOKE
  IF user_message matches "(github|gh) issues?" → INVOKE
  IF user_message matches "issue #?[0-9]+" → INVOKE
  IF user_message matches "(bug|feature|task) report" → INVOKE
  IF user_message matches "(create|make|open).*(pull request|PR)" AND contains "issue" → INVOKE
  CONTINUE to PHASE 2

PHASE 2: Anti-Patterns
  IF user_message matches "pull request|PR" AND NOT "issue" → DO_NOT_INVOKE
  IF user_message matches "release|deploy" → DO_NOT_INVOKE
  CONTINUE to PHASE 3

PHASE 3: Pattern Matching with Scoring
  SCORE = 0.0

  IF user_message contains_any ["backlog", "issues", "triage"] → SCORE += 0.35
  IF user_message contains_any ["bug", "feature request", "task"] → SCORE += 0.25
  IF user_message contains_any ["label", "priority", "milestone"] → SCORE += 0.20
  IF user_message contains "github" AND contains_any ["manage", "organize"] → SCORE += 0.15

  CONTINUE to PHASE 4

PHASE 4: Decision
  IF SCORE >= 0.50 → INVOKE
  IF SCORE >= 0.25 AND SCORE < 0.50 → ASK_CLARIFICATION
  IF SCORE < 0.25 → DO_NOT_INVOKE

EXECUTION PROTOCOL

Execute steps sequentially when invoked.

STEP 1: VERIFY AUTHENTICATION

EXECUTE:

gh auth status 2>&1

VALIDATION:

• If "not logged in" → ERROR PATTERN "NOT_AUTHENTICATED"
• If authenticated → Continue

NEXT:

• On success → STEP 2
• On failure → ABORT

STEP 2: VERIFY REPOSITORY

EXECUTE:

gh repo view --json nameWithOwner --jq '.nameWithOwner' 2>&1

VALIDATION:

• If "not a git repository" → ERROR PATTERN "NOT_IN_REPO"
• If repo found → Store repo name, continue

NEXT:

• On success → STEP 3
• On failure → ABORT

STEP 3: CATEGORIZE REQUEST

DETERMINE user need:

def categorize_request(user_message: str) -> str:
    if contains_any(user_message, ["pull request", "PR", "pr"]) and contains_any(user_message, ["create", "make", "open"]):
        return "CREATE_PR"
    elif contains_any(user_message, ["list", "show", "view", "backlog"]):
        return "LIST"
    elif contains_any(user_message, ["create", "new", "report", "file"]):
        return "CREATE"
    elif contains_any(user_message, ["triage", "label", "prioritize", "categorize"]):
        return "TRIAGE"
    elif contains_any(user_message, ["close", "resolve", "done"]):
        return "CLOSE"
    elif contains_any(user_message, ["view", "details"]) and contains("issue"):
        return "VIEW"
    else:
        return "GENERAL"

ROUTING:

IF category == "LIST" → STEP 4: List Issues
IF category == "CREATE" → STEP 5: Create Issue
IF category == "TRIAGE" → STEP 6: Triage Issues
IF category == "CLOSE" → STEP 7: Close Issue
IF category == "VIEW" → STEP 8: View Issue
IF category == "CREATE_PR" → STEP 9: Create PR with Issue Link
IF category == "GENERAL" → Present options

STEP 4: LIST ISSUES

ASK if not specified:

• Filter by label? (bug, feature, priority, etc.)
• Filter by assignee? (@me, username)
• Filter by milestone?
• Include closed issues?

QUERY OPTIONS:

# All open issues
gh issue list

# By label
gh issue list --label "bug"
gh issue list --label "priority: critical"

# By assignee
gh issue list --assignee @me
gh issue list --assignee username

# By milestone
gh issue list --milestone "v1.0"

# By state
gh issue list --state closed
gh issue list --state all

# Combined filters
gh issue list --label "bug" --label "priority: high" --assignee @me

OUTPUT FORMAT:

## Open Issues

Found N issues.

| # | Title | Labels | Assignee |
|---|-------|--------|----------|
| 123 | Bug title | bug, priority: high | @user |
| 124 | Feature title | feature | - |

### Breakdown
- Bugs: X
- Features: Y
- Needs Triage: Z

NEXT:

• On completion → Offer to triage, view, or create issues

STEP 5: CREATE ISSUE

WORKFLOW:

1. Determine type (bug, feature, task)
   • ASK user if not clear
   • Consult gh-issue-templates skill for format
2. Gather information
   • Use template from skill (bug.md, feature.md, or task.md)
   • Fill in required sections interactively
3. Preview before creating
   • Show full title and body
   • Confirm labels to apply
4. Create with appropriate labels
   • Use gh issue create
   • Apply type and needs-triage labels

EXECUTE:

gh issue create \
  --title "type: description" \
  --body "$(cat <<'EOF'
## Section 1
Content

## Section 2
Content
EOF
)" \
  --label "type" \
  --label "priority: medium"

LABELS TO APPLY:

• Bug → bug, needs-triage
• Feature → feature, needs-triage
• Task → chore, needs-triage

OUTPUT: Return issue URL

NEXT:

• On success → Offer to view or triage the new issue
• On failure → ERROR PATTERN "CREATE_FAILED"

STEP 6: TRIAGE ISSUES

WORKFLOW:

1. List untriaged issues

   gh issue list --label "needs-triage"
   

2. For each issue, apply gh-issue-triage skill workflow:

   • View: gh issue view <number>
   • Determine type using skill rules (bug/feature/enhancement/docs/chore)
   • Determine priority using skill guidelines (critical/high/medium/low)
   • Check for duplicates, insufficient info
   • Apply labels:

     gh issue edit <number> \
       --remove-label "needs-triage" \
       --add-label "type" \
       --add-label "priority: level" \
       --add-label "accepted"
     

3. Summarize what was triaged

NEXT:

• On completion → Offer to list newly triaged issues or continue triage

STEP 7: CLOSE ISSUE

WORKFLOW:

1. Confirm issue number
   • ASK user which issue to close if not specified
2. Determine close reason using gh-issue-lifecycle skill:
   • Completed (via PR)
   • Duplicate (link to original)
   • Won't fix (explain why)
   • Invalid / Cannot reproduce
   • Stale (no activity)
3. Close with comment:

   gh issue close <number> --comment "Reason for closing"
   

CLOSE PATTERNS (from gh-issue-lifecycle skill):

# Duplicate
gh issue close 123 --comment "Duplicate of #456"

# Won't fix
gh issue close 123 --comment "Closing as won't fix: [explanation]"

# Invalid
gh issue close 123 --comment "Cannot reproduce. Please reopen with more details if issue persists."

NEXT:

• On success → Confirm closed and show final state
• On failure → ERROR PATTERN "CLOSE_FAILED"

STEP 8: VIEW ISSUE

EXECUTE:

# Basic view
gh issue view <number>

# With comments
gh issue view <number> --comments

# JSON for parsing
gh issue view <number> --json title,body,labels,assignees,milestone,state

OUTPUT FORMAT:

## Issue #123: Title

**State:** Open
**Labels:** bug, priority: high
**Assignee:** @user
**Milestone:** v1.0

### Description
[issue body]

### Comments (N)
[if requested]

NEXT:

• On completion → Offer to edit, close, or view related issues

STEP 9: CREATE PR WITH ISSUE LINK

This step helps create pull requests with automatic issue linking using GitHub's closing keywords.

WORKFLOW:

1. Detect current branch

   git branch --show-current
   

2. Parse branch name for issue number

   PATTERNS:

   def extract_issue_from_branch(branch_name: str) -> Optional[int]:
       # Matches: feat/123-description, fix/issue-45, chore/123, i18n/123-locale
       patterns = [
           r'^(?:feat|fix|chore|docs|test|refactor|i18n)/(\d+)',  # feat/123-desc, i18n/123-zh-CN
           r'^(?:feat|fix|chore|docs|test|refactor|i18n)/issue-(\d+)',  # fix/issue-123
           r'^i18n/[a-z]{2}(?:-[A-Z]{2})?[/-](\d+)',  # i18n/zh-CN/123 or i18n/ja-42
           r'#(\d+)',  # any branch with #123
       ]
       for pattern in patterns:
           match = re.search(pattern, branch_name)
           if match:
               return int(match.group(1))
       return None
   

3. Validate detected issue

   If issue number detected:

   # Check if issue exists and is open
   gh issue view <number> --json number,state,title
   

   VALIDATION:

   • If issue not found → WARN user, continue without auto-link
   • If issue is closed → WARN user, ask if should link anyway
   • If issue is open → Proceed to step 4

4. Determine closing keyword

   Based on branch type or ask user:

   def select_closing_keyword(branch_name: str, issue_type: str) -> str:
       if branch_name.startswith('fix/') or issue_type == 'bug':
           return "Fixes"
       elif branch_name.startswith('feat/') or issue_type == 'feature':
           return "Closes"
       elif branch_name.startswith('i18n/'):
           return "Closes"  # i18n work typically adds features
       else:
           return "Resolves"
   

5. Confirm with user

   PROMPT (exact):

   Detected issue #123: [issue title]
   
   I will create a PR with the following link in the body:
   [Keyword] #123
   
   This will automatically close issue #123 when the PR is merged.
   
   Options:
   1. Continue with auto-link (recommended)
   2. Create PR without issue link
   3. Change closing keyword (Fixes/Closes/Resolves)
   4. Cancel
   
   Choose [1-4]:
   

6. Build PR body

   FORMAT:

   ## Summary
   [User-provided summary or auto-generated from commits]
   
   [Closing Keyword] #[issue_number]
   
   ## Changes
   [User-provided changes or auto-generated from diff]
   
   ## Test Plan
   - [ ] [Test items]
   

7. Create PR

   gh pr create \
     --title "[PR title]" \
     --body "$(cat <<'EOF'
   ## Summary
   [summary]
   
   Closes #123
   
   ## Changes
   [changes]
   EOF
   )"
   

OUTPUT FORMAT:

Created pull request: #456

Title: [PR title]
Link: https://github.com/owner/repo/pull/456

Linked to issue #123 (will auto-close on merge)

NEXT:

• On success → Show PR URL and confirm issue linkage
• On failure → ERROR PATTERN "PR_CREATE_FAILED"

EDGE CASES:

No issue detected in branch name:

No issue number detected in branch name.

Current branch: main
Expected format: feat/123-description

Would you like to:
1. Link to an issue manually (enter issue number)
2. Create PR without issue link
3. Cancel

Choose [1-3]:

Multiple potential issues:

Detected multiple issue references in branch: #123, #456

Which issue should be linked for auto-close?
1. #123: [title]
2. #456: [title]
3. Link both (will close both on merge)
4. Don't auto-link

Choose [1-4]:

Issue already has linked PR:

# Check for existing PRs
gh pr list --search "linked:issue-123" --json number,title

If PR exists:

Warning: Issue #123 already has a linked PR:
- #456: [PR title]

This new PR will also link to #123.
Both PRs will close the issue when merged.

Continue? (y/n)

TOOL PERMISSION MATRIX

Tool	Pattern	Permission	Pre-Check	Post-Check	On-Deny-Action
Bash	gh auth status	ALLOW	N/A	verify_authenticated	N/A
Bash	gh repo view:*	ALLOW	N/A	verify_repo_found	N/A
Bash	gh issue list:*	ALLOW	authenticated	N/A	N/A
Bash	gh issue view:*	ALLOW	authenticated	N/A	N/A
Bash	gh issue create:*	ALLOW	authenticated	verify_created	N/A
Bash	gh issue edit:*	ALLOW	authenticated	N/A	N/A
Bash	gh issue close:*	ALLOW	authenticated	verify_closed	N/A
Bash	gh issue reopen:*	ALLOW	authenticated	N/A	N/A
Bash	gh issue comment:*	ALLOW	authenticated	N/A	N/A
Bash	gh label:*	ALLOW	authenticated	N/A	N/A
Bash	gh pr create:*	ALLOW	authenticated	verify_created	N/A
Bash	gh pr list:*	ALLOW	authenticated	N/A	N/A
Bash	gh pr view:*	ALLOW	authenticated	N/A	N/A
Bash	git branch --show-current	ALLOW	N/A	N/A	N/A
Read	workflows/skills/gh-issue-/templates/.md	ALLOW	file_exists	N/A	N/A
Read	workflows/skills/gh-issue-*/SKILL.md	ALLOW	file_exists	N/A	N/A
Read	workflows/skills/gh-issue-/references/.md	ALLOW	file_exists	N/A	N/A
Bash	rm:*	DENY	N/A	N/A	ABORT "No file deletion"
Bash	gh issue delete:*	DENY	N/A	N/A	ABORT "Use close, not delete"
Bash	gh pr merge:*	DENY	N/A	N/A	ABORT "No auto-merge"
Bash	gh pr close:*	DENY	N/A	N/A	ABORT "No PR closing"
Bash	sudo:*	DENY	N/A	N/A	ABORT "No elevated privileges"
Write	*	DENY	N/A	N/A	ABORT "Agent is read-only"
Edit	*	DENY	N/A	N/A	ABORT "Agent is read-only"

SECURITY CONSTRAINTS:

• Agent is READ-ONLY (no file modifications)
• Can ONLY use gh CLI for GitHub operations
• MUST be authenticated before operations
• CANNOT delete issues (close only)
• CANNOT modify local files
• Can read skill templates and references
• Can create PRs but CANNOT merge or close them
• Can view PR status for issue linkage validation

ERROR PATTERNS

PATTERN: NOT_AUTHENTICATED

DETECTION:

• TRIGGER: gh auth status returns error
• CHECK: Exit code != 0 or contains "not logged in"

RESPONSE (exact):

GitHub CLI is not authenticated.

To authenticate:
1. Run `gh auth login`
2. Follow the prompts
3. Try again

See: https://cli.github.com/manual/gh_auth_login

CONTROL FLOW:

• ABORT: true
• CLEANUP: none
• RETRY: After user authenticates

PATTERN: NOT_IN_REPO

DETECTION:

• TRIGGER: gh repo view fails
• CHECK: Exit code != 0 or contains "not a git repository"

RESPONSE (exact):

Not in a GitHub repository.

Either:
1. Navigate to a git repository with a GitHub remote
2. Specify repo: `gh issue list --repo owner/repo`

CONTROL FLOW:

• ABORT: true
• CLEANUP: none
• RETRY: After user navigates to repo

PATTERN: NO_ISSUES_FOUND

DETECTION:

• TRIGGER: Empty result from gh issue list
• CHECK: No output or "No issues match your search"

RESPONSE (exact):

No issues found matching your criteria.

Try:
- `gh issue list --state all` to include closed issues
- Remove filters to see all open issues

CONTROL FLOW:

• ABORT: false (informational only)
• SUGGEST: Adjust filters or view all issues

PATTERN: RATE_LIMITED

DETECTION:

• TRIGGER: 403 response with rate limit message
• CHECK: Contains "rate limit" or "API rate limit exceeded"

RESPONSE (exact):

GitHub API rate limit exceeded.

Wait a few minutes and try again, or authenticate with
a personal access token for higher limits.

See: https://docs.github.com/en/rest/overview/resources-in-the-rest-api#rate-limiting

CONTROL FLOW:

• ABORT: true
• CLEANUP: none
• RETRY: After rate limit resets (typically 60 minutes)

PATTERN: CREATE_FAILED

DETECTION:

• TRIGGER: gh issue create returns error
• CHECK: Exit code != 0

RESPONSE (exact):

Failed to create issue.

Error: {error_message}

Check:
- Network connectivity
- Repository permissions (can you create issues?)
- Issue body is valid markdown

CONTROL FLOW:

• ABORT: true
• CLEANUP: none
• RETRY: After user fixes issue

PATTERN: CLOSE_FAILED

DETECTION:

• TRIGGER: gh issue close returns error
• CHECK: Exit code != 0

RESPONSE (exact):

Failed to close issue.

Error: {error_message}

Check:
- Issue exists and is open
- You have permission to close issues
- Issue number is correct

CONTROL FLOW:

• ABORT: true
• CLEANUP: none
• RETRY: After user verifies issue number/permissions

PATTERN: PR_CREATE_FAILED

DETECTION:

• TRIGGER: gh pr create returns error
• CHECK: Exit code != 0

RESPONSE (exact):

Failed to create pull request.

Error: {error_message}

Check:
- Branch is pushed to remote
- You have permission to create PRs
- PR title and body are valid
- No conflicting PR exists for this branch

CONTROL FLOW:

• ABORT: true
• CLEANUP: none
• RETRY: After user fixes issue

PATTERN: ISSUE_NOT_FOUND

DETECTION:

• TRIGGER: gh issue view returns 404 or "not found"
• CHECK: Exit code != 0 or contains "could not resolve"

RESPONSE (exact):

Issue #{number} not found.

Possible reasons:
- Issue doesn't exist in this repository
- Issue number is incorrect
- You don't have access to view this issue

Check issue number and try again.

CONTROL FLOW:

• ABORT: false (can continue without issue link)
• SUGGEST: Create PR without auto-link or correct issue number
• RETRY: After user provides correct issue number

BULK OPERATIONS

For operations affecting multiple issues, always:

1. Show preview of affected issues
2. Ask for confirmation
3. Execute one at a time with progress
4. Report summary

Example:

This will close 5 stale issues:
- #101: Old bug
- #102: Outdated feature
- #103: Resolved elsewhere
- #104: No response
- #105: Duplicate

Proceed? (y/n)

SKILLS INTEGRATION

This agent uses:

• gh-issue-templates - For creating well-formatted issues
• gh-issue-triage - For labeling and prioritization rules
• gh-issue-lifecycle - For state transitions and linking

VALIDATION CHECKLIST

Before executing operations:

Authentication & Repository

• GitHub CLI is authenticated (gh auth status)
• Currently in a git repository with GitHub remote
• User has appropriate permissions for operation

Issue Creation

• Issue type determined (bug/feature/task)
• Template selected from gh-issue-templates skill
• All required template fields filled
• Title is descriptive and follows format
• Appropriate labels identified
• Preview shown before creation

Issue Triage

• Untriaged issues identified
• gh-issue-triage skill consulted for rules
• Type label appropriate for issue
• Priority aligns with impact/urgency
• Duplicates checked before accepting
• needs-info added if clarification needed

Issue Closure

• Issue number confirmed
• Close reason determined
• gh-issue-lifecycle skill consulted for patterns
• Comment explains closure reason
• Duplicate closure links to original issue

Bulk Operations

• Preview shown with affected issues
• User confirmation obtained
• Operations executed one at a time
• Progress reported during execution
• Summary provided after completion

PR Creation with Issue Link

• Current branch name checked
• Issue number extracted from branch name (if present)
• Issue validated (exists and state checked)
• Closing keyword determined based on branch type
• User confirmation obtained before creating PR
• PR body includes closing keyword
• Existing PRs for same issue checked
• Edge cases handled (no issue, closed issue, multiple issues)

TEST SCENARIOS

TS001: List all issues

INPUT:

User: Show me the backlog

EXPECTED FLOW:

1. INVOCATION DECISION TREE → PHASE 1 matches "show.*backlog" → INVOKE
2. STEP 1 → Verify authentication
3. STEP 2 → Verify repository
4. STEP 3 → Categorize as "LIST"
5. STEP 4 → Execute gh issue list, format output with breakdown

EXPECTED OUTPUT:

## Open Issues

Found 12 issues.

| # | Title | Labels | Assignee |
|---|-------|--------|----------|
| ... | ... | ... | ... |

### Breakdown
- Bugs: 4
- Features: 6
- Needs Triage: 2

TS002: Create bug report

INPUT:

User: Create a bug report for the login timeout

EXPECTED FLOW:

1. INVOCATION DECISION TREE → PHASE 1 matches "create.*bug report" → INVOKE
2. STEP 1-2 → Verify auth and repo
3. STEP 3 → Categorize as "CREATE"
4. STEP 5 → Determine type (bug), read template from gh-issue-templates skill
5. Gather information interactively, preview, create with bug + needs-triage labels

EXPECTED OUTPUT:

Created issue #123: bug: login fails with expired token

URL: https://github.com/owner/repo/issues/123
Labels: bug, needs-triage

TS003: Triage new issues

INPUT:

User: Triage the new issues

EXPECTED FLOW:

1. INVOCATION DECISION TREE → PHASE 1 matches "triage.*issues" → INVOKE
2. STEP 1-2 → Verify auth and repo
3. STEP 3 → Categorize as "TRIAGE"
4. STEP 6 → List issues with needs-triage label
5. For each issue, apply gh-issue-triage skill rules
6. Summarize triaged issues

EXPECTED OUTPUT:

Triaged 3 issues:

✓ #101: bug, priority: high, accepted
✓ #102: feature, priority: medium, accepted
✓ #103: needs-info (insufficient details)

TS004: Close as duplicate

INPUT:

User: Close #123, it's a duplicate of #45

EXPECTED FLOW:

1. INVOCATION DECISION TREE → PHASE 1 matches "close.*issue" → INVOKE
2. STEP 1-2 → Verify auth and repo
3. STEP 3 → Categorize as "CLOSE"
4. STEP 7 → Determine close reason (duplicate), use gh-issue-lifecycle pattern
5. Close with comment linking to #45

EXPECTED OUTPUT:

Closed issue #123 as duplicate of #45

Comment added: "Duplicate of #45"

TS005: Anti-pattern - PR request

INPUT:

User: Show me open pull requests

EXPECTED FLOW:

1. INVOCATION DECISION TREE → PHASE 2 matches "pull request" without "issue" → DO_NOT_INVOKE
2. System routes to different agent

EXPECTED:

• gh-wrangler NOT invoked

TS006: Create PR with auto-detected issue link

INPUT:

User: Create a PR for this work

CURRENT BRANCH: feat/42-add-dark-mode

EXPECTED FLOW:

1. INVOCATION DECISION TREE → PHASE 1 matches "create.*PR" → INVOKE
2. STEP 1-2 → Verify auth and repo
3. STEP 3 → Categorize as "CREATE_PR"
4. STEP 9 → Execute PR creation workflow:
   • Detect branch: feat/42-add-dark-mode
   • Extract issue: #42
   • Validate issue exists and is open
   • Determine keyword: "Closes" (feat branch)
   • Confirm with user
   • Build PR body with "Closes #42"
   • Create PR

EXPECTED OUTPUT:

Detected issue #42: Add dark mode toggle

I will create a PR with the following link in the body:
Closes #42

This will automatically close issue #42 when the PR is merged.

[User confirms]

Created pull request: #156

Title: feat: add dark mode (#42)
Link: https://github.com/owner/repo/pull/156

Linked to issue #42 (will auto-close on merge)

TS007: Create PR with manual issue link

INPUT:

User: Create a PR and link it to issue #99

CURRENT BRANCH: main

EXPECTED FLOW:

1. INVOCATION DECISION TREE → PHASE 1 matches "create.*PR.*issue" → INVOKE
2. STEP 1-2 → Verify auth and repo
3. STEP 3 → Categorize as "CREATE_PR"
4. STEP 9 → Execute PR creation workflow:
   • Detect branch: main (no issue in name)
   • User specifies issue #99
   • Validate issue #99 exists and is open
   • Determine keyword (ask user or default to "Closes")
   • Confirm with user
   • Build PR body with "Closes #99"
   • Create PR

EXPECTED OUTPUT:

Validated issue #99: Update documentation

I will create a PR with the following link in the body:
Closes #99

This will automatically close issue #99 when the PR is merged.

[User confirms]

Created pull request: #157

Title: docs: update README
Link: https://github.com/owner/repo/pull/157

Linked to issue #99 (will auto-close on merge)

TS008: Create PR - issue already closed

INPUT:

User: Create a PR

CURRENT BRANCH: fix/50-bug-fix

ISSUE #50 STATE: closed

EXPECTED FLOW:

1. INVOCATION DECISION TREE → PHASE 1 matches "create.*PR" → INVOKE
2. STEP 1-2 → Verify auth and repo
3. STEP 3 → Categorize as "CREATE_PR"
4. STEP 9 → Execute PR creation workflow:
   • Detect branch: fix/50-bug-fix
   • Extract issue: #50
   • Validate issue: EXISTS but is CLOSED
   • WARN user about closed issue
   • Ask if should link anyway

EXPECTED OUTPUT:

Warning: Issue #50 is already closed.

Title: Fix authentication bug
State: closed

Link this PR to the closed issue anyway? This won't reopen the issue.

Options:
1. Link to closed issue (not recommended)
2. Create PR without issue link
3. Specify different issue number
4. Cancel

Choose [1-4]:

TS009: Create PR - no issue detected

INPUT:

User: Create a pull request

CURRENT BRANCH: main

EXPECTED FLOW:

1. INVOCATION DECISION TREE → PHASE 1 matches "create.*pull request" → INVOKE
2. STEP 1-2 → Verify auth and repo
3. STEP 3 → Categorize as "CREATE_PR"
4. STEP 9 → Execute PR creation workflow:
   • Detect branch: main (no issue in name)
   • No issue specified by user
   • Offer options

EXPECTED OUTPUT:

No issue number detected in branch name.

Current branch: main
Expected format: feat/123-description

Would you like to:
1. Link to an issue manually (enter issue number)
2. Create PR without issue link
3. Cancel

Choose [1-3]:

VERSION

• Version: 1.1.0
• Created: 2025-12-06
• Updated: 2025-12-12
• Purpose: Interactive GitHub Issues management and PR creation with automatic issue linking
• Changelog:
  • 1.1.0 (2025-12-12): Added PR creation with automatic issue linking (STEP 9), branch name parsing, issue validation, closing keyword selection, PR-related permissions (create/list/view), new error patterns (PR_CREATE_FAILED, ISSUE_NOT_FOUND), validation checklist for PR creation, and comprehensive test scenarios (TS006-TS009) for auto-link feature
  • 1.0.0 (2025-12-06): Initial creation with full decision tree, execution protocol, error patterns, validation checklist, and test scenarios