skills.rest
twlines
twlinesCOMMUNITY
Explore all skills by this author →
GitHub

pr-preparation

Enforce commit message formatting, change scope limits, and pre-commit validation checks.

Updated Feb 5, 2026
Search Tags:#git#code review#commit#agent#standards#pr
One-click install
npx skills add https://github.com/twlines/maslow --skill pr-preparation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-preparation
Source: https://github.com/twlines/maslow/tree/main/skills/pr-preparation
Command: npx skills add https://github.com/twlines/maslow --skill pr-preparation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that agent-generated code changes adhere to strict commit message formatting, change scope limitations, and pre-commit checks, preventing messy and inconsistent code contributions.

Core Features & Use Cases

  • Commit Message Formatting: Enforces a specific agent(scope): {card title} format.
  • Change Scope Control: Limits changes to under 400 lines and targets only necessary files.
  • Pre-Commit Validation: Mandates removal of debug statements, unused imports, and any types.
  • Use Case: When an AI agent completes a task, this Skill guides it to produce a clean, well-formatted commit that is easy for human reviewers to understand and integrate.

Quick Start

Ensure your commit message follows the format agent(ollama): {card title} and only includes changes directly related to the task.

Frequently Asked Questions about pr-preparation

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

FAQPage Schema
How do I enforce commit message formatting for AI agent generated code?▼

To enforce commit message formatting for AI agent generated code, this Skill mandates a specific `agent(scope): {card title}` structure, ensuring consistent and readable git commit messages for human reviewers.

What are the best practices for limiting change scope in AI agent pull requests?▼

Limiting change scope in pull requests requires restricting modifications to under 400 lines and targeting only necessary files. This ensures focused contributions and efficient code review.

What pre-commit validation checks should I run on AI generated code?▼

Pre-commit validation checks for AI generated code must include removing debug statements, unused imports, and `any` types to guarantee type safety and maintain code quality standards.

Can I use this to standardize agent commit output for software development workflows?▼

Yes, you can use this to standardize agent commit output for software development workflows. It enforces strict adherence to project-specific guidelines, ensuring maintainability and review efficiency.

Why does my AI agent produce messy and inconsistent code contributions?▼

AI agents produce messy and inconsistent code contributions without enforced commit message formatting, change scope limitations, and pre-commit checks. This Skill applies these standards to prevent such issues.

Related Skills

Explore More Software Engineering Skills→
leary-pokenleary-poken
1

databricks-mlflow-evaluation

Run MLflow GenAI evaluate() to score agent outputs with configurable scorers.

Community
Advanced
tikazyqtikazyq
5

code-review

Review pull requests for correctness, quality, test coverage, security, and performance.

Community
Intermediate
NeoLabs-SystemsNeoLabs-Systems
23

requesting-code-review

Automate code review with static security scanning and quality checks.

Official
Advanced
liuminxin45liuminxin45
95

speckit-commit

Create validated multi-repository commits with CoreRuntime commit-message compliance.

Community
Advanced