oat-project-pr-progress

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.

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.

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.

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.

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.

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.