post-pr-review

Post-merge cleanup tasks after a GitHub PR are automated by running a standardized checklist flow that archives tracking files, updates documentation, manages versioning, and deletes feature branches. This ensures a clean and auditable project state once changes are merged to main.

Updating changelog and documentation after a PR merge is handled by automating post-merge housekeeping to ensure relevant documents reflect the change. This includes standardized updates to READMEs, API docs, architecture notes, and changelog entries for a clean release state.

Version tagging and branch deletion in a post-merge cleanup workflow function by applying git versioning tags to releases and optionally deleting the feature branch. The process syncs local and remote records to finalize release artifacts and maintain project hygiene.

No specific dependencies are required to run post-merge housekeeping and issue closure for GitHub workflows. The Skill operates independently to archive artifacts, tag releases, close related issues, and prepare stakeholder notifications via a standardized checklist.

Yes, post-merge cleanup can automatically prepare stakeholder notifications and close related issues. The workflow standardizes release hygiene by tagging releases, updating references, and finalizing notifications to ensure all parties are informed after merging to main.

If post-merge documentation updates and archival tracking files are out of sync, running the post-merge cleanup flow will re-standardize project records. It archives tracking files, ensures documents reflect the change, and syncs local and remote git records for an auditable state.