knowledge-pr

Convert knowledge buffer changes into GitHub issues and pull requests with CI gating.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill knowledge-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-pr
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/knowledge-pr
Command: npx skills add https://github.com/hirokimry/vibecorp --skill knowledge-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns accumulated knowledge-buffer changes into a controlled GitHub issue and pull request workflow, so updates can reach main without manual coordination or risky direct pushes.

Core Features & Use Cases

  • Issue-to-PR automation: Creates a tracking issue, opens a pull request, and prepares auto-merge for buffered knowledge changes.
  • Safety gates: Prevents duplicate open requests, requires push validation, and keeps main protected behind CI and review.
  • Operational use case: Use it when review findings, session notes, or documentation edits have built up in knowledge/buffer and need to be published to the repository in a repeatable way.

Quick Start

Ask the assistant to run the knowledge-pr workflow for the current repository so buffered knowledge changes are turned into an issue, a pull request, and an auto-merge-ready update.

Frequently Asked Questions about knowledge-pr

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

FAQPage Schema
How do I automate pull requests for repository knowledge base updates?

Automate pull requests for repository knowledge base updates by batching buffered changes into a tracking issue and PR flow. This workflow prevents risky direct pushes by creating an issue, opening a pull request, and preparing auto-merge for main branch delivery.

What is the best way to publish buffered knowledge changes to main without manual coordination?

The best way to publish buffered knowledge changes is using an issue-to-PR automation workflow. It creates a GitHub tracking issue, opens a pull request, and prepares auto-merge, safely delivering review-harvest and session-harvest updates to main.

Does auto-merge pull request workflow protect the main branch behind CI and review?

Yes, auto-merge pull request workflows protect main behind CI and CodeRabbit review gating. The workflow requires push validation and applies safety gates to keep the main branch secure during repository automation.

Can I use repository automation to prevent duplicate open issues for knowledge buffer sync?

Yes, repository automation can prevent duplicate open issues for knowledge buffer sync. The workflow features duplicate open-issue detection to ensure only one tracking issue and pull request exist for buffered changes before auto-merge setup.

How do I batch review-harvest and session-harvest updates before production release?

Batch review-harvest and session-harvest updates by accumulating changes in a knowledge buffer. The workflow synchronizes these buffered updates into a tracked GitHub issue and pull request flow for controlled main branch delivery.

When do I need an issue tracking workflow for GitHub knowledge base maintenance?

You need an issue tracking workflow for GitHub knowledge base maintenance when review findings, session notes, or documentation edits build up in a buffer. It turns accumulated changes into a repeatable issue and pull request flow for production release.