Skip to content

ahstn/oceans-llm / .agents/skills/merge-dependabot

merge-dependabot

Verified

Explicitly invoke to review and merge this repository's open Dependabot PRs one at a time.

Merge Dependabot PRs

Invocation: $merge-dependabot. Invoking this skill authorizes sequential merges of the selected Dependabot PRs.

  1. List open Dependabot PRs, for example: mise exec -- gh pr list --repo ahstn/oceans-llm --state open --app dependabot --limit 100. Inspect diffs, actual resolved versions, review feedback, mergeability, and CI; do not trust titles alone.
  2. Order by dependency relationships first. Otherwise group by ecosystem and shared lockfile, handle smaller independent updates before broader runtime/authentication changes, and leave blocked PRs until repaired. Explain the chosen order briefly.
  3. Process one PR at a time. Refresh its head SHA and checks after each preceding merge. Resolve conflicts or dependency failures in an isolated worktree; preserve unrelated local changes and keep lockfiles consistent with manifests. Run applicable mise checks and the verification planner; follow verify-oceans-admin for runtime surfaces and include its report in any created PR.
  4. Wait for applicable CI to pass on the latest head. Inspect failures before retrying; stop work on a PR when a substantive failure cannot be resolved within the dependency update, report the blocker, and continue independent PRs. Never bypass checks, branch protections, or reviews.
  5. Read the repository's allowed merge methods. Merge with gh pr merge <number> --repo ahstn/oceans-llm --merge --match-head-commit <verified-sha> when merge commits are allowed. Confirm state: MERGED before advancing; never queue all PRs for auto-merge.
  6. Re-list open Dependabot PRs and report merged PRs in order, fixes, verification, and anything remaining. Do not silently expand the batch to newly created PRs.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall