research-merge
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.
npx skills add majiayu000/claude-skill-registry --skill research-merge --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 p
- Overview
- User Interaction Pattern
- Processing Workflow
- Step 1: Detect Research Branches
- Step 2: Preview Content
- Step 3: User Decision
- Step 4: Execute Merge
- Step 5: Summary Report
- Issue Generation
- Title Format
- Body Format
- Labels
- Error Handling
- Research Document Standard
git status --porcelain If dirty, prompt user to commit or stash first git merge --squash origin/claude/research-[topic]-[session-id] mkdir -p docs/research Move any root-level research docs git mv RESEARCH*.md docs/research/ 2>/dev/null || true git mv *_RESEARCH.md docs/research/ 2>/dev/null || true git commit -m "docs(research): merge [topic] research from web session Merged from: [branch-name] gh issue create --title "[Research] [Topic Title]" --body "[generated-body]" --label "research,documentation"
What does the research-merge skill do?
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.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill research-merge --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.