Repository navigation
v1.3.0 · Submit and Deploy skills
Added
submittakes a branch to a PR ready for review and stops before the merge. It commits pending task changes, pushes, opens or updates the PR, marks it ready for review, and waits for its checks, the same waydeploydoes up to that point. When you run it again after review feedback, it re-requests review from each reviewer who asked for changes. Its report lists any steps the workflow gives the agent after the merge, such as closing tickets or verifying production, because no agent runs after a person merges.deploylabels its PRagent-mergewhen the agent expects to merge it without waiting for anyone's review or approval, so reviewers can tell its PRs from ones awaiting their review. It creates the label when the repository lacks it.deployremoves the label whenever it stops without merging and adds it back on a later run that can merge.submitalso removes it.
Changed
- The README,
help-snappedly, andsetup-snappedly-skillsnow end the main workflow withsubmit, and presentdeployas the way to skip human review and have the agent merge.
Updating existing repositories
npx skills update updates only the skills you have installed, so add submit with npx skills add snappedly/skills --skill submit.
Rerun setup-snappedly-skills to update the main workflow in docs/agents/workflow.md so it ends with submit and offers deploy to skip human review. Setup keeps an ending your team chose in place of the old default.
Update the installed skills with npx skills update, add submit, then rerun setup-snappedly-skills in each repository.