finalize

Automating git branch cleanup and documentation before a pull request requires orchestrating end-of-branch workflows to synchronize design docs, context files, and user-facing docs. This Skill dispatches agents to update documentation based on branch changes before handling commit squashing and PR creation.

Keeping design docs and project context updated when finishing a feature branch is done by running an automated end-of-branch workflow. The process dispatches specialized agents to perform diff analysis and update architecture docs, CLAUDE.md context, and user-facing documentation automatically.

Yes, you can automatically squash commits and open pull requests from the terminal using GitHub CLI integration. The workflow orchestrates the entire pull request lifecycle by creating changesets, squashing commit history, pushing to remote, and opening the PR for review.

Yes, GitHub CLI is required to automate pull request creation and documentation sync for this workflow. The orchestration relies on GitHub CLI integration alongside internal documentation agents to perform diff analysis, commit squashing, and PR creation.

Automated workflow for documentation synchronization should be used when maintaining complex design-doc-driven repositories with strict documentation standards. It eliminates manual overhead by ensuring architecture docs, project context, and user-facing docs remain perfectly updated before merging.

Yes, finalize works with design-doc-driven repositories to update CLAUDE.md context. It automatically synchronizes context files and user-facing documentation by dispatching specialized agents to analyze branch changes and update repository documentation accordingly.