closeout

Automate pre-Pull Request updates to file headers, AGENTS.md, specs, and work item statuses.

14|Updated Jun 4, 2026
One-click install
npx skills add https://github.com/Cogni-DAO/node-template --skill closeout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: closeout
Source: https://github.com/Cogni-DAO/node-template/tree/main/.openclaw/skills/closeout
Command: npx skills add https://github.com/Cogni-DAO/node-template --skill closeout

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the tedious and error-prone process of preparing a branch for a Pull Request, ensuring all documentation, code headers, and work item statuses are accurate and consistent.

Core Features & Use Cases

  • Automated Documentation Updates: Ensures file headers, AGENTS.md, and specs accurately reflect code changes.
  • Work Item Management: Updates the status, PR number, and reviewer for the associated work item.
  • Use Case: Before submitting a feature branch for review, run this Skill to automatically update TSDoc headers, ensure AGENTS.md is current, and mark the work item as 'Done'.

Quick Start

Run the closeout skill to perform the pre-PR finish pass for the current branch.

Frequently Asked Questions about closeout

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

FAQPage Schema
How do I automate pre-PR checks and documentation updates for my feature branch?

Pre-PR finish pass automation updates file headers, AGENTS.md, and specifications to align code changes with work items. It enforces writing rules and validation checks to update work item statuses, ensuring documentation integrity before pull request submission.

What is included in an automated pre-PR finish pass for a pull request?

A pre-PR finish pass updates TSDoc file headers, AGENTS.md, and specifications to reflect code changes accurately. It also updates work item statuses, PR numbers, and reviewer assignments to maintain documentation integrity before code review.

How do I ensure my AGENTS.md and code headers match my latest branch changes?

To ensure AGENTS.md and code headers match branch changes, run an automated pre-PR finish pass. This updates file headers and specifications, enforcing validation checks to maintain documentation integrity and coherence with assigned work items.

Can I automatically update work item status and PR numbers before submitting a code review?

Automating work item management during a pre-PR finish pass updates the status, PR number, and reviewer for the associated work item. This ensures accurate tracking and documentation coherence before submitting the branch for code review.

What writing rules and validation checks are required for pre-PR documentation updates?

Pre-PR documentation updates require adherence to specific writing rules and validation checks to maintain documentation integrity. These checks verify that file headers, AGENTS.md, and specifications accurately reflect code changes before pull request completion.