pr-formatter

Format TogetherOS pull requests with category tags, keywords, and pre-push validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/coopeverything/TogetherOS --skill pr-formatter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-formatter
Source: https://github.com/coopeverything/TogetherOS/tree/main/.claude/skills/pr-formatter
Command: npx skills add https://github.com/coopeverything/TogetherOS --skill pr-formatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill formats TogetherOS pull requests with proper category, keywords, and a merge-ready body, ensuring consistency and faster reviews.

Core Features & Use Cases

  • Auto-selects Cooperation Path category from module
  • Generates 3-5 relevant keywords
  • Formats PR body with exact structure for automation
  • Runs pre-push validation checks
  • Addresses Codex/Copilot comments until all checks green

Quick Start

Say "create PR" or "format PR" to generate a merge-ready PR body, select a Cooperation Path, and add keywords. Then run pre-push checks locally and push to trigger CI.

Frequently Asked Questions about pr-formatter

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

FAQPage Schema
How do I automate pull request formatting and validation?

PR formatting automation enforces consistent structure, category tagging, and keyword generation across pull requests. This Skill auto-selects the Cooperation Path, generates 3-5 keywords, formats the PR body to a fixed template, and validates merge readiness before push.

What pre-push checks should I run before merging a pull request?

Pre-push validation includes branch sync, merge conflict detection, TypeScript compilation, test execution, and CI readiness verification. This Skill runs these checks automatically to catch issues before triggering CI pipelines.

Can I enforce a consistent PR body structure across my team?

Yes. This Skill formats PR bodies with an exact mandated template, ensuring all team members follow the same structure for category, keywords, and description. Automation prevents manual inconsistencies and speeds up reviews.

How do I generate relevant keywords for pull requests automatically?

Keyword generation analyzes the PR content and module context to produce 3-5 relevant keywords automatically. This ensures PRs are properly tagged for discovery and workflow routing without manual effort.

Does this work with pull request workflows in TogetherOS?

This Skill is designed specifically for TogetherOS pull requests. It integrates module-to-path mapping, auto-selects the Cooperation Path category, and formats PRs to meet TogetherOS automation and merge-readiness requirements.