Finalize a development branch by merging, creating a pull request, or discarding.
npx skills add https://github.com/withakay/research --skill ito-finish
Please help me install this Agent Skill. Skill: ito-finish Source: https://github.com/withakay/research/tree/main/.opencode/skills/ito-finish Command: npx skills add https://github.com/withakay/research --skill ito-finish
This Skill streamlines the finalization process of a development branch, providing structured options for merging, pull requests, or cleanup after all tests pass.
Run the ito-finish skill to finalize your development branch after passing all tests.
High-intent search queries and answers about installing and using this skill.
Branch management finalization is automated by providing structured options for merging, creating pull requests, or discarding the development branch. The process requires passing tests first, then generating cleanup instructions and suggesting integration steps based on the base branch.
The best way to finalize a development branch is using structured options to merge, push a pull request, keep, or discard it. CLI-generated cleanup instructions guide the merging and archiving actions, while integration suggestions adapt to the base branch and tracked ITO changes.
Yes, branch finalization requires git for managing the development branch operations, and it possibly uses ITO for tracking changes. This setup ensures that test verification is completed before any merge, pull request, or discard actions are executed.
Yes, you can keep your development branch. The finalization process offers multiple options including merging, pushing a pull request, keeping the branch, discarding it, or archiving ITO changes, allowing you to choose the appropriate path for your workflow.
Cleanup instructions after merging a development branch are generated directly by the CLI. These instructions provide specific guidance on archiving actions and integrating your work based on the base branch and any associated ITO changes.
Verifying tests before merging or creating a pull request ensures that only passing code is finalized. This test verification step is a prerequisite that prevents broken code from entering the base branch during the branch management process.
alo-expGuide merge, PR, or cleanup decisions after tests pass in Git workflows.
klaidliadonAudit local git branches and worktrees against GitHub pull request state.
santanapolEnforce atomic commits and conventional commit messages for git workflows.
ethicalcapitalAutomate development branch finalization with merge, pull request, or cleanup options.
