Change Integrator FAQs

Question 1

What are the prerequisites for running Change Integrator?

Accepted Answer

To use this skill effectively, you need the GitHub CLI (gh) installed and authenticated, a merged PR number, the original feature branch name, and a repository structure that utilizes standardized documentation paths.

Question 2

What capabilities does it provide for project management?

Accepted Answer

Through GitHub CLI integration, the skill can programmatically update your project board items to 'Done' and append key learnings to a standardized RETROSPECTIVE.md file, ensuring your team's project tracking and insights are always up to date.

Question 3

How does this skill improve my productivity?

Accepted Answer

It eliminates manual 'repository housekeeping.' By automating documentation moves and branch cleanup, it reduces the risk of working with stale branches or outdated specs, allowing you to move directly to your next task without leaving behind technical or administrative debt.

Question 4

When should I use this skill in my workflow?

Accepted Answer

You should trigger this skill immediately after a PR has been merged to the main branch. It is designed to finalize the development cycle, ensuring your repository remains clean and your documentation is perfectly aligned with the current state of the code.

Question 5

What does the Change Integrator skill do?

Accepted Answer

The Change Integrator skill automates repetitive tasks following a Pull Request merge. It handles the deletion of local and remote feature branches, moves draft specifications to the source-of-truth directory, and updates project retrospectives and GitHub board statuses automatically.

Change Integrator

Change Integrator

Características Principales

Casos de Uso

Características Principales

Casos de Uso