PremiumEmail Triage Automation
- Read full threads
- Sort into 3 buckets
- Draft in your voice
- Approve & send
← All skills · Automation · PR Description Writer

Premium
Premium
Free
PremiumAn example of what this Skill produces. Sample content, shown for illustration.
Pull request — sample Changes: 3 | Why: 2 | Tests: 3 (3 passed, 0 failed, 0 not run, 0 not recorded) | Risks: 2 | Gaps: 0 | Errors: 0 | Warnings: 0 Ready to paste — every section is present and the input had no errors. Summary: 1. Return the cached result when content is unchanged in the save path; 2. Add a GET /sessions/:id/result endpoint that serves the cached result; 3. Show a "Cached" badge on the session page when the result comes from cache. Testing: Run the save twice with unchanged content — Pass; Open the cached result endpoint for a finished session — Pass; Load the session page for a cached result — Pass. Door: Two-way door — no irreversible step mentioned; cheap to roll back. Blast radius: api · ui · code. What this description is not: a description describes the change; it does not approve it — a reviewer still reads the diff.
The cached-save change is ready — write the PR description a reviewer can actually use.Read https://skillu.dev/install/agent.md, then install the PR Description Writer skill (pr-description-writer)./pr-description-writer, and describe what you want in plain words.No. It means every section is present and the input had no errors — the description is complete, not the change. A reviewer still reads the diff, and a failing test in the Testing table is a finding, not a blocker for the description.
It is listed as Not recorded in the Testing table, and the warnings name it. The report never assumes a test passed — a description that hides an unrun test is worse than no description.