conventions-check

Validate pull request titles, descriptions, and scope against repository conventions.

95|4|Updated Apr 12, 2026

Search Tags:#code quality #code review #pull request #repository conventions #PR validation

Ready to run

npx skills add https://github.com/try-works/role-model --skill conventions-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventions-check
Source: https://github.com/try-works/role-model/tree/main/.agents/skills/conventions-check
Command: npx skills add https://github.com/try-works/role-model --skill conventions-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures pull requests adhere to specific repository conventions, enhancing code quality and consistency.

Core Features & Use Cases

PR Convention Validation: Checks PR titles, descriptions, and scope against repository guidelines.
Non-Intrusive Feedback: Flags clear violations without second-guessing the author's intent.
Use Case: Before merging a PR, use this Skill to review its adherence to the repository's contribution conventions, ensuring a consistent codebase.

Quick Start

Run the 'conventions-check' skill to verify the pull request meets the repository's conventions.

Frequently Asked Questions about conventions-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate a pull request against repository conventions?▼

To validate a pull request against repository conventions, use a convention checker to review PR titles, descriptions, and scope. This ensures adherence to contribution guidelines and flags clear violations for code consistency.

What is PR convention validation and when do I need it?▼

PR convention validation is the process of checking pull request metadata against repository guidelines. You need it before merging a PR to ensure code consistency and adherence to established contribution standards.

Does PR validation check the author's intent or just the PR scope?▼

PR validation checks the PR scope, titles, and descriptions for clear violations without second-guessing the author's intent. It provides non-intrusive feedback to ensure adherence to repository contribution conventions.

What's the best way to ensure PR titles and descriptions meet contribution guidelines?▼

The best way to ensure PR titles and descriptions meet contribution guidelines is to run a conventions check. It validates PR metadata against repository configuration, identifying clear violations to maintain codebase consistency.

Do I need repository configuration access to check pull request adherence?▼

Yes, you need access to PR metadata and repository configuration to check pull request adherence. The validation process relies on these inputs to compare PR titles and descriptions against established contribution conventions.

Why does PR validation focus on clear violations instead of intent?▼

PR validation focuses on clear violations instead of intent to provide non-intrusive feedback. This ensures code consistency and adherence to repository conventions without second-guessing the author's original design decisions.