Use this skill when a dependabot dependency update PR fails.
npx skills add https://github.com/googleapis/google-cloud-rust --skill unblock-dep-update
You need to help unblock a dependency update.
The user should give you a PR number.
PR_NUMBER=... # e.g. 6133
The first thing to do is to inspect the build failure.
You can determine the commit SHA with:
COMMIT_SHA=$(gh pr view "$PR_NUMBER" --json commits --jq '.commits[-1].oid')
You can enumerate the failed build IDs with:
FAILED_BUILDS=$(gcloud builds list \
--project=rust-sdk-testing \
--region=us-central1 \
--filter="status='FAILURE'" \
--limit=100 \
--format="json" | jq -r --arg SHA "$COMMIT_SHA" '.[] | select(.substitutions.COMMIT_SHA == $SHA) | .id')
You can look at the last lines of output with:
BUILD_ID=${FAILED_BUILDS[0]} # Typically one build is sufficient.
gcloud builds log "$BUILD_ID" --project=rust-sdk-testing --region=us-central1 | tail -n 200
In the output, identify the specific command that failed, and why. e.g. a
cargo test -p google-cloud-<package>.
gh pr checkout ${PR_NUMBER}
Reproduce the build failure locally. Then iteratively fix the error.
When the command succeeds, report success!
Explain the changes and show the diff to the user.
Determine a good commit message for the changes.
COMMIT_MSG=... # e.g. "update foo to be more like bar"
Determine the upstream branch we checked out.
BRANCH=$(git branch --show-current)
Suggest to the user how to commit the changes and push them upstream. e.g.:
> To commit these changes and push them to the dependabot branch, run:
>
> `
> git commit -m "${COMMIT_MSG}" .
> git push upstream HEAD:${BRANCH}
> `
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take googleapis/unblock-dep-update from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.