change-integrator

Automates post-merge integration of specs, retrospectives, and branch cleanup via GitHub CLI.

Updated Jul 13, 2024

Search Tags:#git automation #retrospective #gemini cli #github cli #branch cleanup #post-merge #spec integration

Ready to run

npx skills add https://github.com/Reading-Advantage-Thailand/codecamp-advantage --skill change-integrator-reading-advantage-thailand

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: change-integrator
Source: https://github.com/Reading-Advantage-Thailand/codecamp-advantage/tree/main/.claude/skills/change-integrator
Command: npx skills add https://github.com/Reading-Advantage-Thailand/codecamp-advantage --skill change-integrator-reading-advantage-thailand

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? After a pull request is merged, developers still face tedious cleanup work: moving approved specs into the source-of-truth directory, deleting stale branches, updating project boards, and recording retrospective learnings. This Skill automates that entire post-merge workflow so nothing is forgotten and documentation stays current. ## Core Features & Use Cases - Post-Merge Automation: Verifies the PR is merged, switches to main, deletes the feature branch locally and remotely, and pushes integration commits. - Spec Integration: Moves approved `spec-delta.md` files from `docs/changes/` into `docs/specs/` and commits the change. - Retrospective Maintenance: Appends structured retrospective entries and automatically summarizes older entries with the Gemini CLI when the file exceeds 150 lines. - Use Case: After merging PR #45 for a feature branch, run the integration script with the PR number, branch name, board item ID, and learnings to complete all cleanup and documentation in one step. ## Quick Start Ask the AI to integrate the change for your just-merged PR by providing the PR number, feature branch name, project board item ID, and your went-well and lesson-learned notes.

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 cleanup after a GitHub PR?▼

Run the integrate-change.sh script with the PR number, branch name, board item ID, and retrospective notes. It verifies the merge, deletes the branch, integrates specs, updates the project board, and commits documentation changes to main.

How to keep a retrospective markdown file from growing too large?▼

The script checks RETROSPECTIVE.md line count before each entry. When it exceeds 150 lines, it sends older sprint entries to the Gemini CLI for summarization, preserving the header and historical learnings sections.

What tools are required to run the post-merge integration script?▼

You need the GitHub CLI (gh) installed and authenticated for PR verification and project board updates, plus the Gemini CLI for retrospective summarization. Git must be configured with push access to the repository.

Why does the integration script fail during retrospective summarization?▼

Failures usually mean the gemini CLI is missing, unauthenticated, or the API is unavailable. Run gemini auth to re-authenticate, or temporarily raise the RETROSPECTIVE_MAX_LINES variable to bypass summarization.

Can I perform the post-merge integration steps manually without the script?▼

Yes. The SKILL.md documents manual equivalents: switch to main, delete the branch with git, copy spec-delta.md into docs/specs, update the board via gh project item-edit, and commit the retrospective entry.