pr-note

Generate structured hive-mind notes from pull request data.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/arctype-ventures/arctype-plugins --skill pr-note
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-note
Source: https://github.com/arctype-ventures/arctype-plugins/tree/main/plugins/hive-mind/skills/pr-note
Command: npx skills add https://github.com/arctype-ventures/arctype-plugins --skill pr-note

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR teams spend time summarizing pull requests for knowledge management; this skill automates creating a structured hive-mind note from PR data.

Core Features & Use Cases

  • Automated PR summarization: fetches PR title, description, commits, files, and reviews to generate a coherent note.
  • Structured metadata: writes a frontmatter with repo, project, author, status, and tags for discovery and categorization.
  • Vault integration: writes to the user's Obsidian vault with a consistent naming schema and favors wikilinks to related vault notes.

Quick Start

Create a hive-mind note summarizing the current PR with structured metadata.

Frequently Asked Questions about pr-note

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically summarize pull requests for my knowledge vault?

Automated PR summarization fetches the title, description, commits, files, and reviews to generate a coherent hive-mind note. It writes structured metadata including repo, project, author, status, and tags directly to your vault.

How does automated PR summarization work with Obsidian vault integration?

Vault integration writes structured PR notes to your Obsidian vault using a consistent naming schema. It generates frontmatter with repo, project, author, status, and tags, while favoring wikilinks to connect related vault notes.

What pull request data is needed to generate structured hive-mind notes?

To generate hive-mind notes, the skill parses PR title, body, files, commits, reviews, labels, and state. A configured hive mind vault path and access to PR data are required to write the notes.

Can I use this for code-review documentation across multiple repositories?

This skill applies to code-review workflows, knowledge vaulting, and project documentation across repositories. It writes structured metadata for each PR note to enable discovery and categorization within your vault.

What is the best way to automate pull request documentation for a knowledge base?

Automating PR documentation involves parsing PR data to generate a structured hive-mind note with frontmatter and a narrative. This ensures consistent metadata and vault integration, replacing manual summarization efforts.