Skip to content
Back to skills

Pr Ready

ASecurity

Get a branch ready for review and keep its pull request green. Use before opening a PR and whenever CI or a review reports something on it.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
code-quality

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add asusoda/platform --skill pr-ready --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pr Ready?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pr Ready
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/asusoda-pr-ready/badge)](https://www.skillsdirectory.com/skills/asusoda-pr-ready)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pr-ready
description: Get a branch ready for review and keep its pull request green. Use before opening a PR and whenever CI or a review reports something on it.
---

Before opening:

1. Run the `check` skill. Push only after every command passes.
2. Read your own diff as a reviewer would: unused code, a leftover debug line, a secret, a comment that justifies instead of describes, a missing doc or registry entry (see `new-module`).
3. Commit subject in the imperative, at most 72 characters. The body says why.

PR body:

- A "Before:" paragraph and an "After:" paragraph in plain language.
- A short "How" list naming the files and decisions a reviewer needs.
- New migration IDs, new environment variables, new org secrets and anything a deployer must do.

On CI failure: reproduce locally, find the cause, fix it, and push. A flaky test is not a cause. Never skip or disable a test, and never force-push someone else's branch.

On review comments: fix small, local requests in the next push. Reply on the thread with the reason when you do not.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.