How do I install the Bump Plugin E2e skill?

Run npx skillmds@latest add grafana/bump-plugin-e2e in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bump Plugin E2e safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bump Plugin E2e?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bump Plugin E2e free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bump Plugin E2e?

grafana (@grafana) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bump Plugin E2e by grafana — Agent Skill

Name: Bump Plugin E2e
Author: grafana

File contents

Bump @grafana/plugin-e2e in create-plugin template

Overview

Updates the @grafana/plugin-e2e devDependency in the create-plugin common template to the latest published npm version, then commits and opens a draft PR.

Steps

1. Get the latest version

npm view @grafana/plugin-e2e version

Save the output - this is <NEW_VERSION>.

2. Check the current version

Read packages/create-plugin/templates/common/_package.json and note the current @grafana/plugin-e2e semver range (line ~20).

Note the semver range prefix (e.g. ^, ~, or exact). If the version number already matches <NEW_VERSION>, stop - nothing to do.

3. Update _package.json

Replace only the version number, preserving the existing range prefix exactly.

Example (prefix was ^, keep it ^):

- "@grafana/plugin-e2e": "^3.5.0",
+ "@grafana/plugin-e2e": "^3.6.0",

4. Create a worktree, commit and push

Use a git worktree so the current workspace is never disturbed.

WORKTREE="/tmp/plugin-tools-e2e-bump-$$"
BRANCH=create-plugin/bump-plugin-e2e-<NEW_VERSION>

git worktree add "$WORKTREE" -b "$BRANCH" main

Edit the _package.json inside the worktree (same relative path: packages/create-plugin/templates/common/_package.json), then commit and push:

git -C "$WORKTREE" add packages/create-plugin/templates/common/_package.json
git -C "$WORKTREE" commit -m "Create Plugin: bump @grafana/plugin-e2e to ^<NEW_VERSION>"
git -C "$WORKTREE" push -u origin "$BRANCH"

git worktree remove "$WORKTREE"

5. Open a draft PR

Use the repo PR template structure. Title format: Create Plugin: Bump @grafana/plugin-e2e to <NEW_VERSION>

gh pr create --draft \
  --title "Create Plugin: Bump @grafana/plugin-e2e to <NEW_VERSION>" \
  --label "patch" \
  --label "release" \
  --body "$(cat <<'EOF'
**What this PR does / why we need it**:

Bumps `@grafana/plugin-e2e` to `^<NEW_VERSION>` in the create-plugin common template.

**Which issue(s) this PR fixes**:

Fixes #

**Special notes for your reviewer**:

Automated version bump. Check the [@grafana/plugin-e2e changelog](https://github.com/grafana/plugin-tools/blob/main/packages/plugin-e2e/CHANGELOG.md) for notable changes.
EOF
)"

Post the PR URL to the user as a clickable markdown link, e.g. [grafana/plugin-tools#123](https://github.com/grafana/plugin-tools/pull/123).

---name: bump-plugin-e2edescription: Use when bumping the @grafana/plugin-e2e version in the create-plugin template. Fetches the latest npm version, updates _package.json, commits, and opens a draft PR.---# Bump @grafana/plugin-e2e in create-plugin template## OverviewUpdates the `@grafana/plugin-e2e` devDependency in the create-plugin common template to the latest published npm version, then commits and opens a draft PR.## Steps### 1. Get the latest version```bashnpm view @grafana/plugin-e2e version```Save the output - this is `<NEW_VERSION>`.### 2. Check the current versionRead [packages/create-plugin/templates/common/\_package.json](packages/create-plugin/templates/common/_package.json) and note the current `@grafana/plugin-e2e` semver range (line ~20).Note the semver range prefix (e.g. `^`, `~`, or exact). If the version number already matches `<NEW_VERSION>`, stop - nothing to do.### 3. Update \_package.jsonReplace only the version number, preserving the existing range prefix exactly.Example (prefix was `^`, keep it `^`):```json- "@grafana/plugin-e2e": "^3.5.0",+ "@grafana/plugin-e2e": "^3.6.0",```### 4. Create a worktree, commit and pushUse a git worktree so the current workspace is never disturbed.```bashWORKTREE="/tmp/plugin-tools-e2e-bump-$$"BRANCH=create-plugin/bump-plugin-e2e-<NEW_VERSION>git worktree add "$WORKTREE" -b "$BRANCH" main```Edit the `_package.json` inside the worktree (same relative path: `packages/create-plugin/templates/common/_package.json`), then commit and push:```bashgit -C "$WORKTREE" add packages/create-plugin/templates/common/_package.jsongit -C "$WORKTREE" commit -m "Create Plugin: bump @grafana/plugin-e2e to ^<NEW_VERSION>"git -C "$WORKTREE" push -u origin "$BRANCH"git worktree remove "$WORKTREE"```### 5. Open a draft PRUse the repo PR template structure. Title format: `Create Plugin: Bump @grafana/plugin-e2e to <NEW_VERSION>````bashgh pr create --draft \ --title "Create Plugin: Bump @grafana/plugin-e2e to <NEW_VERSION>" \ --label "patch" \ --label "release" \ --body "$(cat <<'EOF'**What this PR does / why we need it**:Bumps `@grafana/plugin-e2e` to `^<NEW_VERSION>` in the create-plugin common template.**Which issue(s) this PR fixes**:Fixes #**Special notes for your reviewer**:Automated version bump. Check the [@grafana/plugin-e2e changelog](https://github.com/grafana/plugin-tools/blob/main/packages/plugin-e2e/CHANGELOG.md) for notable changes.EOF)"```Post the PR URL to the user as a clickable markdown link, e.g. `[grafana/plugin-tools#123](https://github.com/grafana/plugin-tools/pull/123)`.

Frequently asked questions

Bump Plugin E2e