deps-land

Drives one Dependabot PR through CI verification, screenshot testing, and gated merge handoff.

1|1|Updated Oct 3, 2021
One-click install
npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill deps-land-benjr70
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deps-land
Source: https://github.com/benjr70/Smart-Smoker-V2/tree/main/.claude/skills/deps-land
Command: npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill deps-land-benjr70

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dependabot PRs pile up because each one still needs CI validation, a real-app smoke check, and a merge decision — and doing that by hand for every bump is slow and error-prone. This Skill automates the entire gate-and-merge lane for a single Dependabot PR, driving it to exactly one terminal outcome: merged, handed to a human (HITL), parked as failed, or marked superseded. ## Core Features & Use Cases - Two-tier evidence verification: Runs Tier A (CI green via /pr-watch --bot) and Tier B (a forced six-screenshot real-app tour via /verify-pr --force-tour) before any merge is approved. - Bounded fix loop with sha-keyed markers: Up to 3 fix attempts across both tiers, tracked via PR comment markers keyed to the head sha, so crashed runs resume safely and force-pushes invalidate stale verdicts. - Conflict and security handling: Retitles security bumps to fix(deps): for release-please, nudges @dependabot rebase on conflicting branches, or drives a rebase itself when agent commits exist. - Use Case: A nightly daemon triages open PRs, finds a Dependabot minor bump, and invokes this lane — it verifies CI, captures the six app screenshots, runs the decision gate, and prints a merge command for the caller to execute. ## Quick Start Invoke the skill with the PR number, branch, head sha, and reason, for example: run deps-land on PR #42 with branch dependabot/npm_and_yarn/lodash-4.17.21, the current head sha, reason dependabot, and the security and major flags from triage.

Frequently Asked Questions about deps-land

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically verify and merge Dependabot PRs?

Invoke this lane with the PR number, branch, head sha, and triage reason. It runs CI verification via /pr-watch, a forced screenshot tour via /verify-pr, then a decision gate whose merge command the caller executes — the lane itself never merges.

How are Dependabot PR conflicts handled automatically?

If the branch carries only Dependabot commits, the lane posts '@dependabot rebase' and ends the fire. If agent fix commits exist, it drives the rebase itself via rebase-driver.sh, regenerating lockfile conflicts with npm install --legacy-peer-deps --package-lock-only.

What happens when a major version bump passes all checks?

Major bumps are never merged on machine evidence alone. The lane labels the PR HITL, comments both tier verdicts and a screenshot pointer, and waits for a GitHub approval review before a later fire re-gates and merges the same sha.

Why does verification stop when the PR head sha changes?

All verdict markers are keyed to the head sha, so a force-push or Dependabot rebase invalidates them. The fire ends as superseded and the next fire re-verifies both tiers on the new sha, ensuring approvals never vouch for unseen code.

What is the fix attempt limit for failing dependency bumps?

The cap is 3 attempts total across both verification tiers and all fires, counted from sha-keyed PR comment markers. On exhaustion the PR is drafted, labeled AFK:deps-failed, and commented once, so triage never re-picks it.