# Fetch complete issue details
gh issue view {issue_number} --json \
  title,body,labels,comments,createdAt,updatedAt,state,author

# Search commit messages for issue keywords
git log --oneline --all --since="2025-01-01" --grep="{keyword}"

# Search for GitHub issue references in commits
git log --oneline --all --grep="#{issue_number}"

# Search for related file changes
git log --oneline --all --since="2025-01-01" -- "**/path/to/component*"

# Check if the problematic code pattern still exists
rg "{error_pattern}" --type ts

# Check if fix patterns were added
rg "stopPropagation|preventDefault" --type tsx

# Check if component was refactored/deleted
ls -la src/components/{component}/

# Find PRs that mention the issue
gh pr list --state all --search "#{issue_number}" --json number,title,state,mergedAt

# Find PRs that touched related files
gh pr list --state merged --search "{component_name}" --json number,title,mergedAt

gh issue close {number} --comment "$(cat <<'EOF'
Closing this issue - it has been addressed.

**Resolution:**
- Fixed in PR #{pr_number} / commit {commit_hash}
- The {component} was refactored in {month}
- The original error pattern no longer exists

If you're still experiencing this issue, please open a new issue with current reproduction steps.
EOF
)"

gh issue close {number} --comment "$(cat <<'EOF'
Closing this issue as outdated.

**Reason:**
- {component/feature} has been significantly refactored since this was reported
- The original context no longer applies to current architecture
- This issue is {age} old with no recent activity

If this is still a problem, please open a new issue with:
1. Current reproduction steps
2. Expected vs actual behavior
3. Screenshots/logs if applicable
EOF
)"

## GitHub Issue: #{issue_number}

**Original Report:** {github_url}
**Reported:** {created_date}
**Reporter:** {author}

## Summary
{Updated summary based on current codebase understanding}

## Current State
{What exists in the codebase today}

## Problem
{Clear description of what's wrong}

## Expected Behavior
{What should happen}

## Steps to Reproduce
{Updated steps if original are outdated}

## Technical Notes
- Relevant files: {file_paths}
- Related components: {components}
- Potential approach: {suggestions}

## Original Description
{Include original issue body for reference}

gh issue comment {github_issue_number} --body "$(cat <<'EOF'
Linear ticket created: [{ticket_id}]({linear_url})

This issue is now being tracked in Linear for prioritization and implementation.
EOF
)"

START: Analyze GitHub Issue #{number}
  |
  +-- Is issue < 3 months old?
  |   +-- YES: Higher priority to investigate thoroughly
  |   +-- NO: Check if still relevant to current architecture
  |
  +-- Does issue reference existing component/feature?
  |   +-- YES: Search for related fixes
  |   +-- NO: CLOSE_OUTDATED (component removed)
  |
  +-- Found related PR/commit that fixes it?
  |   +-- YES: CLOSE_FIXED (cite the PR)
  |   +-- NO: Continue investigation
  |
  +-- Does error pattern still exist in code?
  |   +-- YES: Likely still an issue
  |   +-- NO: CLOSE_FIXED (pattern removed)
  |
  +-- Is issue clearly described with reproduction steps?
  |   +-- YES: CREATE_TICKET
  |   +-- NO: Can we infer the problem?
  |       +-- YES: UPDATE_AND_CREATE
  |       +-- NO: CLOSE_CANNOT_REPRODUCE
  |
  +-- END: Take appropriate action