change-integrator

Automate post-merge spec migration, branch cleanup, board updates, and retrospective logging.

Updated Sep 11, 2024
One-click install
npx skills add https://github.com/Reading-Advantage-Thailand/www-reading-advantage --skill change-integrator-reading-advantage-thailand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-integrator
Source: https://github.com/Reading-Advantage-Thailand/www-reading-advantage/tree/main/.claude-old/skills/change-integrator
Command: npx skills add https://github.com/Reading-Advantage-Thailand/www-reading-advantage --skill change-integrator-reading-advantage-thailand

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 essential but often tedious tasks performed after a code Pull Request (PR) is merged, ensuring a clean repository and up-to-date documentation.

Core Features & Use Cases

  • Automated Spec Integration: Moves approved spec files from a temporary location to the main documentation directory.
  • Branch Cleanup: Deletes local and remote feature branches post-merge.
  • Project Board Updates: Marks tasks as complete on project management boards.
  • Retrospective Maintenance: Appends learnings to a retrospective log and automatically summarizes older entries to maintain readability using an LLM.
  • Use Case: After merging a feature branch for a new API endpoint, this Skill automatically integrates its spec, cleans up the branch, updates Jira, and adds the key learnings to the team's retrospective document.

Quick Start

Use the change-integrator skill to integrate the changes from PR number 123, branch name feat/new-api, and project item ID 456, noting that the API documentation was well-received and the lesson learned was to always include OpenAPI specs.

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 tasks like spec migration and branch cleanup?

Automate post-merge integration by running scripts that move spec files to the main directory, delete local and remote feature branches, and update project boards automatically.

Can I use GitHub CLI to update project boards and delete branches after a PR merge?

Yes, GitHub CLI can delete local and remote feature branches and mark tasks complete on project management boards automatically after a pull request is successfully merged.

How does automated retrospective logging work for merged pull requests?

Automated retrospective logging appends team learnings to a log file after a merge, using Gemini CLI to summarize older entries and maintain long-term readability.

Do I need a merged PR and branch name to automate spec file migration?

Yes, you need a merged PR number and branch name to automate spec file migration, with an optional project item ID and change directory provided for updating project boards.

What is the best way to streamline post-merge integration in CI/CD pipelines?

Streamline post-merge integration in CI/CD pipelines by automating branch cleanup, spec integration, and retrospective logging using GitHub Actions and CLI task automation.