Skip to main content

Ready PR Before New Pull Requests

Require ready-pr whenever creating or opening a GitHub pull request

Source: .agents/rules/ready-pr-before-new-pr.mdc

Metadata​

  • name: ready-pr-before-new-pr
  • alwaysApply: true

Content​

Ready PR Before New Pull Requests

When creating or opening a GitHub pull request for this repo, use .agents/skills/ready-pr/SKILL.md as the PR readiness workflow.

Required Practice​

  • Run ready-pr when the user asks to create, open, or prepare a new PR.
  • Let ready-pr perform code review first, then update or create the PR title and description from the branch diff.
  • Do not use standalone pr-description or raw gh pr create as the final PR flow unless ready-pr is blocked by a real prerequisite failure.
  • If ready-pr is blocked, report the exact blocker and do not fake code-review results or PR metadata updates.
  • Preserve the safety rules from the relevant skills: do not commit, push, send Lark messages, or create docs unless the user request and skill workflow allow it.