pr-template

The pr-template skill is a specialized tool designed to automate the creation of high-quality, standardized pull request (PR) descriptions. It is engineered for development teams that prioritize code documentation, review efficiency, and project traceability. By enforcing a consistent structure, this skill ensures that reviewers receive all necessary context to evaluate changes effectively, including business impact, technical implementation choices, and comprehensive verification steps. It is particularly effective for teams using modern web stacks like TanStack Start, FastAPI, Drizzle, and SQLModel, as it encourages linking technical changes to specific issues in Linear and documenting multi-tenant isolation or RLS policy updates.

• Automatically generates a structured markdown template containing sections for Summary, Motivation, Implementation Details, Testing, and a Checklist.

• Enforces strict quality standards, including references to Linear issues (e.g., GREY-123), technical trade-offs, and clear testing strategies (unit, integration, e2e, benchmark).

• Provides a pre-submission checklist to verify style guideline compliance (90 characters for TypeScript, 130 for Python), type hint maintenance, and migration testing.

• Integrates seamlessly into the development lifecycle, supporting fast context switching for developers working on features, bug fixes, or complex refactors.

• Use this skill during the final phase of a feature implementation or bug fix before opening a pull request.

• Expected inputs include the context of your recent commits and the specific Linear issue ID being addressed.

• The generated output is a ready-to-copy markdown block that maintains a professional communication standard across your engineering team.

• Ensure all manual testing steps are documented within the template to minimize review cycles and speed up the merging process.

• The skill is configured to support specific Grey Haven patterns such as the repository pattern and database schema changes, ensuring that all architectural decisions are transparently communicated to team members.