github-pr-issue_skill

This skill helps you manage GitHub issues and PRs non-interactively, fetch reviews, and generate structured summaries according to team standards.

Python

16

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill dcjanus/prompts --skill github-pr-issue

SKILL.md2.7 KB

Overview

This skill automates viewing and updating GitHub Issues and Pull Requests, including comments, review threads, and diffs. It can create or modify PRs and Issues non-interactively while enforcing team naming and description conventions. It returns full URLs after successful creations and ensures current branch state before operations.

How this skill works

The skill fetches PR/Issue metadata, comments, review threads, and diffs from GitHub and presents consolidated summaries. For create/update actions it runs non-interactive Git and GitHub commands, checking git status and performing git fetch/push as needed. When editing titles or bodies it first reads the current content, applies the requested changes, and submits updates without invoking an interactive editor.

When to use it

Inspect a PR including overview, comments, review threads, and diff.
Create an Issue or PR non-interactively following team conventions.
Update PR or Issue title/body while ensuring you modify the latest content.
Summarize PR review comments and rank by severity for response drafting.
Ensure branch is pushed and up-to-date before opening or updating a PR.

Best practices

Always run git fetch and confirm the local branch is clean before creating a PR.
Keep PR titles semantic and short using English prefixes like feat/fix/docs even if body must be another language.
Write PR bodies with ## Why, ## What, and ## Testing sections using short sentences and bullet points.
Limit displayed review comments to 10; indicate if more remain to avoid overwhelming reviewers.
Read the current Issue/PR title and body before modifying to prevent accidental overwrites.

Example use cases

Generate a non-interactive PR with a semantic title and a Why/What/Testing body, then return the PR URL.
Show PR overview plus up to 10 highest-severity review comments and remaining count if applicable.
Create an Issue non-interactively with a concise title and description and return the Issue URL.
Update a PR description: read the current body, apply requested edits, and push the updated body without opening an editor.

FAQ

No. All create and update operations are non-interactive and do not open an editor.

How does it ensure the branch is up-to-date?

It runs git fetch and checks git status; it requires a clean working tree and a successful push before creating a PR.

How are review comments presented?

Comments and threads are consolidated and ordered by severity; up to 10 items are shown with a remaining-count notice if more exist.