aiwg-pr

Name: aiwg-pr
Availability: InStock
Author: fortemi

Standardize pull request and commit delivery workflows for AIWG repositories.

4|Updated Feb 3, 2026

Search Tags:#git #workflow #pull request #compliance #delivery #aiwg

Ready to run

npx skills add https://github.com/Fortemi/HotM --skill aiwg-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aiwg-pr
Source: https://github.com/Fortemi/HotM/tree/main/.agents/skills/aiwg-pr
Command: npx skills add https://github.com/Fortemi/HotM --skill aiwg-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity and compliance risks in AIWG product and workspace deliveries by enforcing strict, policy-aligned pull request and commit workflows.

Core Features & Use Cases

Delivery Policy Enforcement: Automatically determines whether to use direct commits, feature branches, or formal PRs based on project configuration.
Verification Gates: Mandates local typechecking, testing, and linting before any code is pushed to ensure CI stability.
Use Case: When preparing a feature for an AIWG repository, use this skill to ensure your commit messages, branch naming, and PR descriptions strictly adhere to the project's no-attribution and delivery-policy rules.

Quick Start

Use the aiwg-pr skill to prepare and validate a new delivery pull request for the current project.

Frequently Asked Questions about aiwg-pr

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

FAQPage Schema

How do I enforce a standardized git pull request workflow for repository delivery?▼

A pull request workflow enforces strict compliance by automating branch management, executing local verification gates, and generating policy-aligned commit messages to eliminate ambiguity in product deliveries.

How do I generate compliant commit messages without attribution for my project?▼

Generating compliant commit messages without attribution requires enforcing project-specific delivery policies that automatically format commit metadata to strictly adhere to no-attribution rules before any code is pushed.

What is the best way to run verification gates before pushing a feature branch?▼

Running verification gates before pushing a feature branch involves mandating local typechecking, testing, and linting execution to ensure CI stability and validate that the delivery adheres to project-specific delivery modes.

Does this delivery workflow support direct commits or only formal pull requests?▼

The delivery workflow supports both direct commits and formal pull requests by automatically determining the appropriate delivery mode based on your specific project configuration and policy requirements.

Why do my pull requests fail compliance checks in an AIWG-managed repository?▼

Pull requests fail compliance checks when branch management, commit messages, or PR descriptions do not strictly adhere to the project's no-attribution and delivery-policy rules enforced during the delivery lifecycle.