oat-project-pr-progress

Generate progress Pull Request descriptions from OAT artifacts and git history.

1|Updated Jan 26, 2026

Search Tags:#automation #git #project management #code review #pull request #oat

Ready to run

npx skills add https://github.com/tkstang/open-agent-toolkit --skill oat-project-pr-progress

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oat-project-pr-progress
Source: https://github.com/tkstang/open-agent-toolkit/tree/main/.agents/skills/oat-project-pr-progress
Command: npx skills add https://github.com/tkstang/open-agent-toolkit --skill oat-project-pr-progress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of progress Pull Request descriptions for OAT projects, summarizing completed work and linking to relevant artifacts.

Core Features & Use Cases

Automated PR Description Generation: Creates a PR-ready summary grounded in OAT artifacts and git history.
Phase/Range Scoping: Supports PRs for specific project phases (pNN) or explicit git commit ranges.
Use Case: After completing a development phase for your OAT project, use this skill to generate a detailed PR description that includes goals, changes, verification steps, and links to relevant design and plan documents, ready to be submitted to your code repository.

Quick Start

Use the oat-project-pr-progress skill to generate a progress PR description for phase p02.

Frequently Asked Questions about oat-project-pr-progress

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

FAQPage Schema

How do I automatically generate a pull request description from git commits?▼

To automatically generate a pull request description from git commits, this skill reads OAT artifacts like plan.md and spec.md, collects commit history, and summarizes completed work into a PR-ready format. It grounds the summary in your project artifacts and changed files.

How do I create a progress PR for a specific project phase?▼

You can create a progress PR for a specific project phase by scoping the generation to a pNN phase identifier. This collects the git commit history and changed files within that defined phase to produce a targeted PR description.

Can I use the gh CLI to automatically open a PR with a generated description?▼

Yes, you can use the gh CLI to automatically open a PR. After generating the progress PR description from OAT artifacts and git history, the skill optionally opens a pull request directly using the gh CLI.

What is an OAT project progress PR and when do I need to generate one?▼

An OAT project progress PR summarizes completed development work within a git range or phase. You need to generate one after completing a project phase to submit a detailed summary of goals, changes, and verification steps to your repository.

Does the PR generator work without OAT artifacts like design.md?▼

The PR generator reads OAT artifacts like plan.md, spec.md, and design.md to ground the PR summary. Without these artifacts, it cannot link to relevant design and plan documents or effectively summarize the completed project work.

What's the best way to summarize completed work from a git commit range for a code review?▼

The best way to summarize completed work from a git commit range for a code review is using an automated generator. It extracts commit history and changed files, then formats them into a PR description with goals and verification steps.