# Merge Research Branches Into Issues

Research created in Claude Code web sessions can stay scattered across branches. This skill guides review, merging, document organization, and issue creation.

## Install

```bash
npx skillstore add jrc1883/research-merge
```

## Metadata

- Status: approved
- Slug: jrc1883-research-merge
- Skillstore revision: r1
- Version status: missing
- Tree hash: 2fe374b052cd5bbf42864acf459f416b532ebb18198c119c85514d357f0c59c1
- Author: jrc1883
- GitHub username: jrc1883
- License: MIT
- Repository: https://github.com/jrc1883/popkit-claude/tree/main/packages/popkit-research/skills/pop-research-merge/
- Ref: 0519034dad657fb1f7706e0550e962beeda73fdf
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: scripts, external\_commands, network, filesystem
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/jrc1883-research-merge
- Manifest: https://skillstore.pages.dev/api/skills/jrc1883-research-merge/manifest

## Capabilities

- Detects Claude research branches through a research branch detector utility.
- Previews branch topics, document paths, commit counts, and summaries before action.
- Prompts the user to merge, merge with an issue, skip, or delete each branch.
- Documents git commands for squash merging approved research into the main branch.
- Moves research documents into docs/research when they are not already organized.
- Creates GitHub issues from research summaries, tasks, labels, and source metadata.

## Use Cases

- Process mobile research sessions: Merge research created in Claude Code Web into the main repository with organized documentation.
- Turn findings into tracked work: Convert research summaries and implementation tasks into GitHub issues with useful labels.
- Maintain research documentation: Move research documents into a standard docs/research location after approval.

## Prompt Templates

### Review research branches

```
Find Claude research branches, preview each branch, and ask before taking any merge, issue, or delete action.
```

### Merge approved research

```
Process the approved research branch, move its documents to docs/research, and summarize the completed actions.
```

### Create implementation issues

```
Merge approved research and create GitHub issues from the summary, source details, and implementation tasks.
```

### Batch process a research queue

```
Review all claude/research branches, group related topics, propose a processing order, and execute only approved actions.
```

## Limitations

- It is designed only for research branches, not regular feature branches.
- It requires git access and the GitHub CLI for the full workflow.
- It does not resolve merge conflicts automatically.
- Issue quality depends on research documents following the expected format.

## Best Practices

- Review branch previews before approving merge or deletion actions.
- Keep research documents in the expected format with summaries and implementation tasks.
- Confirm the working tree is clean before running merge operations.

## Anti Patterns

- Do not use this workflow for normal feature branches.
- Do not delete remote branches before verifying the merge result.
- Do not create issues from incomplete or unreviewed research notes.

## Security Audit

- Audited at: 2026-07-09T11:13:45.09\+00:00
- Summary: The high certificate/key alerts are false positives because the script only handles path strings for research comparison. The confirmed risks are the documented git and GitHub CLI operations that can merge commits, move files, create issues, and delete remote research branches after user approval. No evidence found for prompt injection, credential exfiltration, or hidden network behavior.

## Stats

- Views: 205
- Downloads: 8
- Favorites: 0
- Popularity score: 0