Agent skill · research science · aiskillstore
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.
Why this skill is useful
Adds a complete executable workflow for processing research branches, including scripts for merging and organizing documentation that the AI cannot generate on its own.
What it needs
Requires popkit-shared installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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: Processing Workflow Step 1: Detect Research Branches Use the researchbranchdetector.py utility: Step 2: Preview Content For each branch, show a preview before prompting: Step 3: User Decision Use AskUserQuestion for each branch: Step 4: Execute Merge Based on user choice: Option A: Merge + Issue (Full Processing) Option B: Merge Only Option C: Skip No action - branch remains for future processing. Option D: Delete Step 5: Summary Report After processing all branches: Issue Generation Title Format Examples: [Research] Claude Code v2.0.65 Features Integration [Research] Audio Feedback Hooks Architecture Body Format Labels Automatically apply: research - Marks as research output documentation - Contains documentation Optionally detect from content: enhancement - If implementation tasks found P1-high / P2-medium / P3-low - From priority metadata Error Handling Situation Response ----------- ---------- Dirty working directory Prompt to commit/stash first Merge conflicts Show conflicts, offer manual resolution gh CLI unavailable Skip issue creation, note in output No doc files Merge anyway, create minimal issue Branch already merged Skip, note in output Research Document Standard For best results, research docs should follow this format: Integration Points Component Role ----------- ------ pop-next-action Calls this skill when branches detected researchbranchdetector.py Core detection logic /popkit:next Entry point for auto-detection /popkit:routine morning Can i …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/research-merge