Research Branch Merge FAQs

Question 1

Do I need the GitHub CLI installed?

Accepted Answer

The GitHub CLI (gh) is recommended for the full experience, as it allows the skill to automatically create issues with labels and checklists directly from your research.

Question 2

What happens to my research documents during the merge?

Accepted Answer

Research documents found in the root or other directories are automatically moved to a standardized 'docs/research/' folder to maintain clean project organization.

Question 3

Can I use this for regular feature branches?

Accepted Answer

This skill is specifically optimized for research branches. It is not recommended for regular feature branches as it uses a squash-merge and doc-reorganization workflow tailored for documentation-heavy research.

Question 4

Will it merge my code automatically?

Accepted Answer

No. The skill is designed to always prompt the user for a decision using an interactive menu, allowing you to choose between merging, skipping, or deleting the branch.

Question 5

How does this skill identify a research branch?

Accepted Answer

The skill scans your remote repository for branches following the 'claude/research-*' naming convention or branches containing specific research-related documentation patterns.

Research Branch Merge

主要功能

使用场景

Research Branch Merge

主要功能

使用场景