github-pr-description skillA
github-pr-description is agent-read markdown (skill) from tailcallhq/forgecode: Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Create PR Description Generate comprehensive pull request descriptions and create PRs using GitHub CLI. ## Workflow ### 1. Verify Prerequisites Check that there are changes to create a PR for: ```bash # Get current branch git branch --show-current # Verify branch is not main/master # Verify there are commits ahead of main git log origin/main..HEAD --oneline ``` If on main/master or no commits ahead, inform the user there's nothing to create a PR for. ### 2. Analyze Changes Gather context about the changes: ```bash # Get commit messages git log origin/main..HEAD --pretty=format:"%s" # Get diff summary (files changed) git diff origin/main..HEAD --stat # Get actual code changes (sample key files if diff is large) git diff origin/main..HEAD ``` **For large diffs**: Focus on the most meaningful changes. Sample key files rather than reading everything. ### 3. Determine Change Type Classify the PR into one of these categories: - **fix**: Bug fixes, error corrections, resolving issues - **feature**: New functionality, capabilities, or enhancements - **performance**: Speed improvements, optimization, efficiency gains …
Read the whole file at its exact version.
How to install
mdr add tailcallhq/forgecode/github-pr-description@git:20260303.9704bbamdr add tailcallhq/forgecode/github-pr-description@sha256:0eb8bfd663f09081Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_qa3j35pdcgpuekqn)
2 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11292 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tailcallhq/forgecode · 7,637 stars · license Apache-2.0 · pushed 2026-09-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qa3j35pdcgpuekqn GET https://markdownregistry.com/api/v1/resolve?ref=tailcallhq/forgecode/github-pr-description GET https://markdownregistry.com/api/v1/blob/0eb8bfd663f0908166018e6fb98eae7f5a39dac5adc412bbf7264a23bbc4aae3
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.