Skills research-merge

📦

research-merge

Name: research-merge
Author: jrc1883

Content revision r1 Safe ⚡ Contains scripts⚙️ External commands🌐 Network access📁 Filesystem access

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.

Supports: Claude Codex Code(CC)

📊 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "research-merge" from https://skillstore.io/skills/jrc1883-research-merge.md and its manifest at https://skillstore.io/api/skills/jrc1883-research-merge/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/jrc1883-research-merge.md Signed manifest GET /api/skills/jrc1883-research-merge/manifest Signed lockfile GET /api/skills/jrc1883-research-merge/lockfile

Test it

Using "research-merge". One approved research branch about audio feedback hooks.

Expected outcome:

A completion summary lists the merged branch, organized research document, and created GitHub issue.

Using "research-merge". Several research branches with mixed priorities.

Expected outcome:

A branch table shows each topic, commit count, document list, selected action, and next step.

Using "research-merge". A research document with implementation tasks.

Expected outcome:

A GitHub issue draft contains the summary, source branch, documentation links, and task checklist.

Security Audit

Safe

v9 • 7/9/2026 Open versioned report

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.

Files scanned

922

Lines analyzed

Review items

False positives ignored

Capability review items (3)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium

SKILL.md:122-151

Ruby/shell backtick execution

```bash

The bash workflow instructs git merge, git mv, git commit, gh issue create, and git push origin --delete. These commands modify repository and GitHub state, so they require explicit approval and branch validation.

Medium

SKILL.md:155-167

Ruby/shell backtick execution

```bash

This bash block instructs git merge --squash and git commit, which modify the local repository. It is part of the intended workflow but remains a real external command risk.

Medium

SKILL.md:175-180

Ruby/shell backtick execution

```bash

This block instructs git push origin --delete to remove a remote research branch after confirmation. That action is destructive if used on the wrong branch, so it is a real external command risk.

Risk Factors

⚡ Contains scripts (1)

SKILL.md:50-57

⚙️ External commands (41)

🌐 Network access (2)

SKILL.md:142 SKILL.md:161

📁 Filesystem access (2)

SKILL.md:133 SKILL.md:134

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/jrc1883-research-merge/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/jrc1883-research-merge/security.svg)](https://skillstore.io/skills/jrc1883-research-merge?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/jrc1883-research-merge?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/jrc1883-research-merge/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/jrc1883-research-merge.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

jrc1883. (2026). research-merge security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/jrc1883-research-merge/audits/9

BibTeX citation

@techreport{jrc1883-jrc1883-research-merge-2026,
  author = {jrc1883},
  title = {research-merge security audit report (audit version 9)},
  institution = {Skillstore},
  year = {2026},
  number = {9},
  url = {https://skillstore.io/skills/jrc1883-research-merge/audits/9},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "research-merge security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
  - name: "jrc1883"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/jrc1883-research-merge/audits/9"
identifiers:
  - type: other
    value: "skillstore:jrc1883-research-merge:audit:9"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

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.

Try These Prompts

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.

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.