- Home
- Skills
- Technical Documentation
- PR Description Writer Skill
Works with the AI Agents you already use
PR Description Writer Skill
Convert git diffs and commit history into structured, technical pull request descriptions.
Free
PR Description Writer Skill
Example session with this skill installed
Generate a PR description for this diff: it updates auth_service.py to use Argon2 for password hashing instead of SHA-256. Added a unit test in test_auth.py. No tests run yet.
- Read your context and instructions
- Compiled the pr description writer
I have analyzed the diff and drafted a PR description focusing on the hashing algorithm migration and the new test coverage.
PR Description
Summary
Updates the password hashing mechanism in the authentication service from SHA-256 to Argon2 to improve credential security.
What changed
- auth_service.py: Replaced
hashlib.sha256implementation withargon2-cffi. - requirements.txt: Added
argon2-cffias a dependency. - test_auth.py: Integrated a new unit test case for Argon2 hash verification.
Why
Rationale not explicitly provided in context, but code reflects a migration to a more computationally expensive hashing algorithm to mitigate brute-force risks.
Implementation notes
- The implementation uses default Argon2 parameters (Type ID, Time cost 3, Memory cost 65536).
- Existing SHA-256 hashes will need a migration strategy as this PR does not include a multi-algorithm fallback.
How to test
Recommended checks:
- Run
pytest tests/test_auth.pyto verify the new Argon2 implementation. - Perform a manual login flow to ensure the hashing middleware correctly intercepts password strings.
- Verify dependency installation via
pip install -r requirements.txt.
Risks / follow-up
Breaking Change: Existing users with SHA-256 hashes will be unable to log in until a migration script is executed or a fallback mechanism is implemented.
- Follow-up: Implementation of a "rehash on login" strategy is recommended for production deployment.
Next steps
- Copy the Markdown above into your GitHub or GitLab PR description field.
- Run the recommended unit tests and update the "How to test" section with results.
- Confirm the migration strategy for existing user records.
Connects securely to your tools. The creator never sees your data.
About this skill
Writing pull request descriptions is a friction point that slows down shipping. This skill automates the drafting process by transforming git diffs, patches, and commit logs into structured, reviewer-ready Markdown. It ensures every PR clearly communicates what changed and what needs testing without the manual overhead of summarizing code changes.
What it does
- Diff analysis parses git diffs and patches to identify core logic changes and affected components.
- Context integration weaves issue tracker data and developer notes into the narrative to explain the purpose behind the code.
- Implementation mapping groups technical changes by feature or module for easier scanning by reviewers.
- Test categorization distinguishes between tests already executed and recommended verification steps.
- Platform formatting generates Markdown compatible with GitHub, GitLab, and Bitbucket standards.
How it works
- Provide the git diff, commit messages, or a patch file along with any relevant issue context or developer notes.
- The skill analyzes the technical delta to separate evidenced code changes from inferred intent.
- It generates a draft following your team's specific PR template or the default structured format.
- Review the generated summary, implementation notes, and risk assessment before pasting into your VCS.
Frameworks & tools
This skill is platform-agnostic and works with any version control system that uses Markdown for pull/merge requests, including GitHub, GitLab, and Bitbucket. It processes standard git diff formats and plain text commit summaries.
Why this beats prompting it yourself
Generic prompts often hallucinate business logic or claim tests passed when they haven't. This skill follows strict rules to separate evidenced changes from developer intent, ensuring you never misrepresent test results or security implications to your reviewers.
Use cases
- Drafting descriptions for large refactors where manual summaries are tedious.
- Standardizing PR documentation across a distributed engineering team.
- Generating clear changelogs for internal library updates.
- Ensuring consistency between commit history and final PR documentation.
Known limitations
Does not have direct repository access. Requires the user to provide the diff or context manually. Cannot verify if tests actually passed without provided logs.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.
Requires manual input of diffs or commit logs. Cannot autonomously verify test results or security claims. Limited to information present in provided text or files.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 23 days ago
- Free with an Agensi account
Permissions
No special permissions declared or detected