Guide end-of-implementation decisions on merge, PR, delay, or discard.
npx skills add https://github.com/bostonaholic/rpikit --skill finishing-work-bostonaholic
Please help me install this Agent Skill. Skill: finishing-work Source: https://github.com/bostonaholic/rpikit/tree/main/skills/finishing-work Command: npx skills add https://github.com/bostonaholic/rpikit --skill finishing-work-bostonaholic
This skill provides a structured workflow to safely conclude completed implementations, ensuring tests pass and decisions are made about merging, PR creation, delaying, or discarding work.
Review the completed work, verify tests pass, then select and execute one of the finishing options.
High-intent search queries and answers about installing and using this skill.
Finalizing work requires choosing a structured completion path such as merging locally, creating a pull request, delaying, or discarding. The selected option triggers prescribed cleanup procedures to ensure safe and auditable completion of the implementation cycle.
Choosing between merging, pull requests, or discarding is resolved by evaluating structured finishing options after verifying all tests pass. This approach eliminates decision friction by providing clear, prescribed cleanup steps for each available path.
Safely cleaning up a local branch after a merge or pull request involves following prescribed cleanup procedures that identify the base branch and remove residual work. This ensures the repository state remains stable after the finishing decision is executed.
If tests pass but you are not ready to merge, you can select the delay option to keep the work for later. This finishing path ensures the implementation is safely preserved without prematurely merging or discarding the completed code.
Yes, verifying all tests pass is a strict requirement before selecting a finishing option. This prerequisite ensures the implementation is fully validated, enabling a safe decision regarding merging, pull requests, delaying, or discarding the work.
Finishing an implementation requires identifying the base branch to ensure the merge or pull request targets the correct integration point. This step prevents accidental commits to the wrong branch and maintains a clean, auditable project history.
thbehAutomate finishing development branches with test verification, merge or PR options, and cleanup.
mikeyobrienValidate tests and execute merge, pull request, keep, or discard actions.
cookerVerify tests and present four integration options for finishing a development branch.
1Shot-LabsAutomates Git operations including commit generation, branch management, and pull requests.
