Change Integrator FAQs

Question 1

What does the Change Integrator skill do?

Accepted Answer

The Change Integrator skill automates the post-merge development cycle. It cleans up local and remote feature branches, moves approved design specs to your source-of-truth documentation, updates GitHub Project boards, and maintains a concise project retrospective.

Question 2

When should I use this skill?

Accepted Answer

You should trigger this skill immediately after a Pull Request (PR) has been merged into your main branch. It is perfect for finalizing feature implementations, cleaning up repository clutter, and ensuring your documentation reflects the latest code changes.

Question 3

What are the prerequisites for using Change Integrator?

Accepted Answer

To use this skill effectively, you need the GitHub CLI (gh) and Gemini CLI installed and authenticated. You should also ensure you are on the main branch with the latest changes before running the integration commands.

Question 4

Does this skill require a specific project structure?

Accepted Answer

While it is optimized for workflows using a 'docs/changes/' and 'docs/specs/' directory structure, its core features like branch cleanup and project board synchronization can be used in any GitHub-based repository.

Question 5

How does the AI-powered retrospective maintenance work?

Accepted Answer

When your RETROSPECTIVE.md file grows too large, the skill uses the Gemini CLI to automatically summarize older entries. This process preserves key historical learnings and markdown structure while keeping the document readable and manageable for the team.

Change Integrator

Change Integrator

Key Features

Use Cases

Key Features

Use Cases