change-integrator

Automate post-merge integration tasks including spec migration, branch cleanup, and project board updates.

11|3|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/bodangren/git-workflow --skill change-integrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-integrator
Source: https://github.com/bodangren/git-workflow/tree/main/.claude/skills/change-integrator
Command: npx skills add https://github.com/bodangren/git-workflow --skill change-integrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, gemini, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the post-merge integration process, ensuring that approved specifications are moved to their final location, project boards are updated, and the repository is kept clean by removing obsolete branches. It also maintains the RETROSPECTIVE.md file by summarizing older entries to keep it concise.

Core Features & Use Cases

  • Post-Merge Integration: Moves approved specs from docs/changes/ to docs/specs/.
  • Branch Cleanup: Deletes local and remote feature branches after merging.
  • Project Board Updates: Marks tasks as "Done" on GitHub projects.
  • Retrospective Maintenance: Appends new learnings and automatically summarizes older entries using Gemini CLI when the file exceeds a size limit.
  • Use Case: After successfully merging a feature branch for a new API endpoint, you can use this skill to automatically move the associated spec, delete the branch, update the project board, and record the learnings in the retrospective.

Quick Start

Run the change integrator script with the merged PR number, branch name, project item ID, and key learnings.

Frequently Asked Questions about change-integrator

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

FAQPage Schema
How do I automate post-merge branch cleanup and spec migration?

Automating post-merge branch cleanup and spec migration involves moving approved specifications to their final directory and deleting obsolete local and remote Git branches automatically. This skill executes those exact tasks to ensure repository hygiene after merging a feature branch.

Does GitHub CLI support automated project board updates after a merge?

GitHub CLI supports automated project board updates by marking tasks as "Done" on GitHub projects. This skill leverages the CLI combined with Gemini CLI to handle project management updates and documentation summarization during integration.

What is the best way to maintain a concise RETROSPECTIVE.md file?

Maintaining a concise RETROSPECTIVE.md file requires appending new learnings and automatically summarizing older entries when the file exceeds a size limit. This skill uses Gemini CLI to automatically summarize historical retrospective logs and keep the file manageable.

Can I move approved specs from docs/changes/ to docs/specs/ automatically?

You can move approved specs from docs/changes/ to docs/specs/ automatically as part of an automated post-merge integration workflow. This skill handles the spec file migration process directly to ensure approved specifications reach their final location.

Do I need both GitHub CLI and Gemini CLI to run post-merge integration tasks?

You need both GitHub CLI and Gemini CLI to run these post-merge integration tasks effectively. GitHub CLI manages branch cleanup and project board updates, while Gemini CLI handles the documentation summarization for the retrospective log.

Why does my retrospective log keep growing after integrating changes?

A retrospective log keeps growing if older entries are not summarized when the file exceeds a defined size limit. This skill automatically appends new learnings and uses Gemini CLI to summarize historical entries, preventing uncontrolled file growth.