oat-project-pr-final

Generate final Pull Request descriptions from OAT project artifacts and Git history.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/tkstang/open-agent-toolkit --skill oat-project-pr-final
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oat-project-pr-final
Source: https://github.com/tkstang/open-agent-toolkit/tree/main/.agents/skills/oat-project-pr-final
Command: npx skills add https://github.com/tkstang/open-agent-toolkit --skill oat-project-pr-final

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation of final Pull Request descriptions for OAT projects, ensuring all relevant artifacts and review statuses are accurately reflected, and optionally automates PR creation.

Core Features & Use Cases

  • Automated PR Description Generation: Compiles project goals, changes, verification steps, and review outcomes into a comprehensive PR description.
  • Artifact Integration: Gathers information from spec.md, design.md, plan.md, and implementation.md for a complete summary.
  • Optional PR Creation: Integrates with the GitHub CLI (gh) to create the PR automatically after description generation.
  • Use Case: After completing all development phases for a new feature, run this skill to generate a PR description that includes a summary of changes, links to design documents, and final review status, then have it automatically open the PR against the main branch.

Quick Start

Run the oat-project-pr-final skill to generate the final PR description and open the PR.

Frequently Asked Questions about oat-project-pr-final

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

FAQPage Schema
How do I automate pull request description generation from markdown artifacts?

To automate pull request description generation, this skill compiles project goals, changes, and verification steps from spec.md, design.md, plan.md, and implementation.md into a comprehensive PR summary. It validates required artifacts and checks review status before generating the final description.

What is the process for finalizing a project PR from Git history and documentation?

Finalizing a project PR involves validating required artifacts, collecting summaries from various markdown files, archiving active review artifacts, and optionally creating a PR using the GitHub CLI. It updates project state upon completion to reflect the finalized review status.

Do I need the GitHub CLI installed to create pull requests with this automation tool?

Yes, you need the GitHub CLI (gh) installed if you want to automatically create the pull request after description generation. The skill uses the GitHub CLI to optionally open the PR against the main branch directly upon completing the summary compilation.

Can I compile spec, design, and plan markdown files into a single pull request summary?

Yes, you can compile spec.md, design.md, plan.md, and implementation.md files into a single pull request summary. The skill integrates information from these project artifacts to ensure all relevant documentation and review outcomes are accurately reflected.

What happens to active review artifacts when the final PR is generated?

When the final PR is generated, active review artifacts are automatically archived. The skill handles this archiving process and subsequently updates the project state upon completion to ensure the repository reflects the finalized review outcomes accurately.