ワンクリックでManusで任意のスキルを実行

update-dependency

スター0

フォーク0

更新日2026年4月30日 04:30

Use when the user asks to upgrade a specific npm/pnpm dependency (e.g. "upgrade vite", "bump @sveltejs/kit"). Bumps the package to its latest version on a feature branch, verifies the build, and opens a PR.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

kpfefferle

kpfefferle/bluecoats

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Update Dependency

Upgrade a single dependency to its latest version, verify the project still builds and tests pass, and open a PR.

Steps

Confirm the package name. If the user's request is ambiguous (e.g. "upgrade tailwind" — tailwindcss? @tailwindcss/vite? both?), ask before proceeding.
Branch. Create a feature branch named chore/bump-<package> (e.g. chore/bump-vite). Per the project's workflow rule (see .claude/CLAUDE.md → Workflow), never commit dependency bumps directly to main.
Upgrade. Run pnpm update <package> --latest to move it to the latest version (not just within the current semver range). Use pnpm — not npm or yarn.
Verify. Run pnpm lint and pnpm test (which runs Vitest + Playwright). All must pass.
Commit. Use a commit message of the form Bump <package> from <old> to <new>. Pull the old/new versions from the pnpm-lock.yaml diff or pnpm update output.
Open the PR. Push the branch and run gh pr create with a brief summary of what changed and the lint/test results.

Notes

If the upgrade introduces a breaking change that surfaces during lint or test, stop and surface the failure to the user — don't fix the API breakage silently. They may want to defer the bump or scope the migration.
For dependency groups already covered by Dependabot (visible in git log --oneline | grep Bump), check whether a Dependabot PR is already open before creating a duplicate.

このリポジトリの他の Skills

同じリポジトリ

add-score

kpfefferle/bluecoats

Use when the user asks to log/record a result for a Bluecoats DCI event — either a numeric competition score ("log 90.3 for DCI Denton", "the Houston show scored 91.25") or a non-scored result ("Opening Night was an exhibition", "the Dallas show got rained out"). Fills the result into the matching scheduled entry in the season data and opens a PR.

2026-06-300

review-dependabot-prs

kpfefferle/bluecoats

Use when the user asks to review, process, or merge open Dependabot PRs (e.g. "review the dependabot PRs", "merge the open dependency bumps"). Walks each PR through CI check, review, rebase-if-stale, and squash-merge.

2026-05-030

name	update-dependency
description	Use when the user asks to upgrade a specific npm/pnpm dependency (e.g. "upgrade vite", "bump @sveltejs/kit"). Bumps the package to its latest version on a feature branch, verifies the build, and opens a PR.

Update Dependency

Upgrade a single dependency to its latest version, verify the project still builds and tests pass, and open a PR.

Steps

Confirm the package name. If the user's request is ambiguous (e.g. "upgrade tailwind" — tailwindcss? @tailwindcss/vite? both?), ask before proceeding.
Branch. Create a feature branch named chore/bump-<package> (e.g. chore/bump-vite). Per the project's workflow rule (see .claude/CLAUDE.md → Workflow), never commit dependency bumps directly to main.
Upgrade. Run pnpm update <package> --latest to move it to the latest version (not just within the current semver range). Use pnpm — not npm or yarn.
Verify. Run pnpm lint and pnpm test (which runs Vitest + Playwright). All must pass.
Commit. Use a commit message of the form Bump <package> from <old> to <new>. Pull the old/new versions from the pnpm-lock.yaml diff or pnpm update output.
Open the PR. Push the branch and run gh pr create with a brief summary of what changed and the lint/test results.

Notes

If the upgrade introduces a breaking change that surfaces during lint or test, stop and surface the failure to the user — don't fix the API breakage silently. They may want to defer the bump or scope the migration.
For dependency groups already covered by Dependabot (visible in git log --oneline | grep Bump), check whether a Dependabot PR is already open before creating a duplicate.