← ClaudeAtlas

research-mergelisted

Processes research branches from Claude Code Web sessions - merges content, moves docs to docs/research/, and creates GitHub issues. Use when /popkit:next detects research branches or when manually processing research from mobile sessions. Do NOT use for regular feature branches - only for branches matching claude/research-* or containing research documentation.
aiskillstore/marketplace · ★ 329 · Code & Development · score 79
Install: claude install-skill aiskillstore/marketplace
# Research Branch Merge ## Overview Handles the complete workflow for processing research branches created during Claude Code Web sessions: 1. Detect research branches 2. Preview content for user approval 3. Squash-merge to main branch 4. Move docs to standardized location 5. Create GitHub issue from findings 6. Clean up remote branch **Trigger:** Called by `pop-next-action` skill when research branches detected, or directly via `/popkit:research merge`. ## User Interaction Pattern **ALWAYS use AskUserQuestion** for merge decisions: ``` Use AskUserQuestion tool with: - question: "Found research branch: [topic]. How should we process it?" - header: "Research" - options: - label: "Merge and create issue" description: "Squash-merge, move docs, create GitHub issue, delete branch" - label: "Merge only" description: "Squash-merge content without creating issue" - label: "Skip for now" description: "Leave branch for later processing" - label: "Delete branch" description: "Discard research (cannot be undone)" - multiSelect: false ``` ## Processing Workflow ### Step 1: Detect Research Branches Use the `research_branch_detector.py` utility: ```python import sys # No longer needed - install popkit-shared instead from research_branch_detector import ( fetch_remotes, get_research_branches, format_branch_table, get_branch_content_preview, parse_research_doc, generate_issue_body ) # Fetch and detect fetch_remotes() branches = get_r