skills.rest
graysurf
graysurfCOMMUNITY
Explore all skills by this author →
GitHub

close-progress-pr

Finalize and archive GitHub Pull Request progress files with status updates and link patching.

Updated Aug 23, 2026
Search Tags:#automation#workflow#documentation#github#archiving#pr
One-click install
npx skills add https://github.com/graysurf/agent-kit --skill close-progress-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: close-progress-pr
Source: https://github.com/graysurf/agent-kit/tree/main/skills/workflows/pr/progress/close-progress-pr
Command: npx skills add https://github.com/graysurf/agent-kit --skill close-progress-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the finalization and archiving of progress tracking for GitHub Pull Requests, ensuring that completed work is properly marked and its documentation is preserved.

Core Features & Use Cases

  • Automated Archiving: Moves finalized progress files to an archive directory.
  • Status Updates: Sets the progress status to 'DONE' and updates timestamps.
  • PR Body Patching: Updates PR links to point to the base branch and links implementation PRs to planning PRs.
  • Use Case: When a feature PR is ready to be merged and its associated progress tracking is complete, this Skill ensures all related documentation and PR links are updated correctly, maintaining a clean project history.

Quick Start

Use the close-progress-pr skill to finalize and archive the progress for the current PR.

Frequently Asked Questions about close-progress-pr

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

FAQPage Schema
How do I automate archiving GitHub PR progress files when a feature is merged?▼

To automate archiving GitHub PR progress files, this Skill moves finalized progress tracking files to an archive directory, updates their status to DONE, and patches PR body links to the base branch. It links implementation PRs to planning PRs.

What is the best way to finalize and update progress documentation for a merged pull request?▼

Finalizing progress documentation involves setting the progress status to DONE, updating timestamps, and moving the files to an archived directory. This Skill also patches PR body links to point to the base branch to maintain a clean project history.

How does PR body patching work when closing progress tracking for GitHub pull requests?▼

PR body patching updates existing PR links to point to the base branch instead of a specific commit. It also links the implementation PR directly to the original planning PR to preserve the project's documentation history.

Can I defer incomplete checklist items while archiving progress files for a pull request?▼

Yes, you can defer incomplete checklist items while archiving progress files. This Skill handles checklist item deferral during the finalization process, ensuring only completed work is marked DONE and moved to the archive directory.

Does this PR archiving workflow update progress READMEs automatically?▼

Yes, this PR archiving workflow updates progress READMEs automatically. As part of finalizing and archiving the progress tracking files, the Skill ensures the READMEs reflect the updated DONE status and recent timestamps.

When should I use an automated workflow to archive progress files instead of manual cleanup?▼

You should use an automated workflow to archive progress files when a feature PR is ready to be merged and its associated progress tracking is complete. This ensures all related documentation and PR links are updated correctly without manual errors.

Related Skills

Explore More Software Engineering Skills→
jammindevjammindev

status

Summarize project state from git history and GitHub issues and pull requests.

Official
Intermediate
OutlineDrivenOutlineDriven
5

pr-merge-temporal

Merge multiple pull requests into a temporal integration branch for validation.

Official
Advanced
ClementWalterClementWalter
2

GitHub Workflow

Guide GitHub issue workflow with hierarchy, milestones, and automation scripts.

Community
Intermediate
jankneumannjankneumann
4

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes while detecting spec conflicts.

Community
Advanced