Squash merge completed work into the main branch and clean up artifacts.
npx skills add https://github.com/myrtlepn/gran-maestro --skill accept-myrtlepn
Please help me install this Agent Skill. Skill: accept Source: https://github.com/myrtlepn/gran-maestro/tree/main/skills/accept Command: npx skills add https://github.com/myrtlepn/gran-maestro --skill accept-myrtlepn
This Skill automates the finalization of completed work, merging it into the main codebase and cleaning up associated artifacts, ensuring a smooth transition from review to production.
master, clean up the feature branch and worktree, and then check if any other requests were waiting for REQ-001 to be completed, activating them if so.Use the accept skill to finalize and merge the completed work for request REQ-001.
High-intent search queries and answers about installing and using this skill.
To automate merging approved feature branches into the main branch, this Skill performs squash merges to integrate completed work while maintaining a clean project history. It finalizes work by merging the approved worktree and then automatically removing the associated temporary branches.
Dependency management after merging automatically unblocks and activates subsequent dependent requests once a task is successfully accepted. It checks if other requests were waiting for the completed task and triggers them, ensuring the workflow continues seamlessly without manual intervention.
The best way to clean up temporary worktrees and branches after a merge is to use an automated finalization process. This Skill removes temporary worktrees and associated branches immediately after completing a squash merge into the main codebase.
Yes, you can synchronize linked request statuses within a source plan during a merge. This Skill ensures plan synchronization by automatically updating the status of linked requests when the transition from review to completion is finalized.
Yes, this workflow handles the transition from code review to production automatically. It manages the progression from Phase 3 review to Phase 5 completion by executing squash merges, cleaning up artifacts, and activating downstream dependencies without manual steps.
A dependent request remains inactive after a squash merge if the finalization process encounters an issue updating the source plan. Successful acceptance automatically unblocks dependent requests, so inactivity indicates the transition from review to completion was not properly finalized.
luispabonValidate code changes against approved planning artifacts using temporary git worktrees.
ITSaltAutomate a nine-step emergency hotfix workflow for main production branches.
weebcoder101Trigger skill pipelines on GitHub events, cron schedules, or file changes.
tkerseyFinish GitHub pull requests by updating branches, monitoring CI, and squash-merging.