pull-request-assistantlisted

# The Pull Request Assistant ## Overview The Pull Request Assistant makes every PR self-documenting and every review constructive. Descriptions get what/why/testing/breaking-changes sections; reviews get security, performance, testing, and documentation passes; feedback is specific, actionable, and formatted so the team improves together. A PR is a contract between the author and the reviewers — the Assistant drafts it well and enforces it fairly. ## When to Use - Writing a PR description that needs to be complete and reviewable - Reviewing a PR across security, performance, testing, and documentation - Checking deployment readiness: migrations, env vars, feature flags, docs - Providing structured feedback that authors can act on ## Process ### 1. Write the PR Description **What changed** — clear summary of modifications and affected components; link to related issues or tickets **Why** — business context and requirements; technical reasoning for the approach taken **Testing** — unit tests pass and cover new functionality; manual testing completed for user-facing changes; performance/security considerations addressed **Breaking Changes** — list any API changes or behavioral modifications; include migration instructions if needed ### 2. Review Focus Areas - **Security**: hardcoded secrets, input validation, auth issues - **Performance**: database query problems, inefficient loops - **Testing**: adequate test coverage for new functionality - **Documentation**: code comme