# Manage GitHub PRs and Issues

GitHub review and release work can require several commands and repeated context gathering. This skill collects PR context and guides issue or PR changes with structured workflows.

## Install

```bash
npx skillstore add dcjanus/github-pr-issue
```

## Metadata

- Status: approved
- Slug: dcjanus-github-pr-issue
- Skillstore revision: r1
- Version status: missing
- Tree hash: 16da9c4c600331d486c5f9bb184c59958c023f79343d00fdbd836306e464e6af
- Author: DCjanus
- GitHub username: DCjanus
- License: MIT
- Repository: https://github.com/DCjanus/prompts/tree/master/skills/github-pr-issue
- Ref: 7e9e368dc1a370f2040369ebcd0db06d90cb48e5
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 66
- Public page: https://skillstore.pages.dev/skills/dcjanus-github-pr-issue
- Manifest: https://skillstore.pages.dev/api/skills/dcjanus-github-pr-issue/manifest

## Capabilities

- View GitHub issues through GitHub CLI guidance.
- Fetch PR metadata, comments, reviews, files, commits, stats, bodies, and diffs through read\_pr.py.
- Format concise pull request titles and descriptions using team-oriented sections.
- Create GitHub issues and pull requests with body files instead of interactive editors.
- Edit existing issue or PR titles and descriptions after reading current content.
- Report GitHub API rate limit details when requested.

## Use Cases

- Review Incoming Pull Requests: Gather a PR summary, changed files, comments, reviews, and diff context before preparing review feedback.
- Prepare Release Pull Requests: Create a clear PR title and body with summary, key changes, tradeoffs, testing, and notes.
- Create Structured Issues: Open GitHub issues with concise titles and body text without entering an interactive editor.

## Prompt Templates

### View a Pull Request

```
Use this skill to summarize <PR URL>. Include the title, body, changed files, and testing notes.
```

### Create an Issue

```
Create a GitHub issue for this bug. Use a concise title and a clear body with impact and reproduction details.
```

### Draft a Pull Request

```
Prepare a pull request for the current branch. Include summary, key changes, constraints, testing, and reviewer notes.
```

### Analyze PR Discussion

```
Read <PR URL> with reviews, review comments, issue comments, changed files, stats, and diff. Identify unresolved risks and next actions.
```

## Limitations

- Requires GitHub CLI authentication and network access to GitHub.
- The helper script only supports github.com pull request URLs.
- Can modify remote GitHub resources when write commands are approved.
- Does not replace repository-specific review, compliance, or release policies.

## Best Practices

- Confirm the target repository, branch, and PR or issue URL before running write commands.
- Request only the PR sections needed to reduce token use and API calls.
- Read existing issue or PR content before replacing titles or descriptions.

## Anti Patterns

- Do not run mutating GitHub commands without explicit user approval.
- Do not paste access tokens into prompts, issue bodies, or pull request descriptions.
- Do not use the helper script for non-github.com URLs or unrelated repository hosts.

## Security Audit

- Audited at: 2026-07-05T09:41:58.632\+00:00
- Summary: Most static findings in SKILL.md are false positives caused by Markdown backticks and code fences. The helper script legitimately invokes GitHub CLI authentication and contacts the GitHub API; no obfuscation, prompt injection, or third-party exfiltration was found. The remaining concerns are sensitive token handling and documented workflows that can modify GitHub state.

## Stats

- Views: 176
- Downloads: 7
- Favorites: 0
- Popularity score: 0