Add E2E Test Suite
crowdin/crowdin-cli
Adds a new end-to-end (e2e) test suite for the Crowdin CLI under tests/e2e/suites/, exercising real CLI commands against a freshly-created Crowdin project.
Use after changing extension code, to prove it works: which test tier to run, the red-before-green rule, and what to record in the PR test plan.
Install Verifying Changes
$ npx skills add Mr-Quin/danmaku-anywhere --skill verifying-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Mr-Quin/danmaku-anywhere verifying-changes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Mr-Quin/danmaku-anywhere.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/verifying-changes .claude/skills/verifying-changes && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "verifying-changes" agent skill from https://github.com/Mr-Quin/danmaku-anywhere/tree/master/.claude/skills/verifying-changes into .claude/skills/verifying-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-changes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Mr-Quin/danmaku-anywhere/tree/master/.claude/skills/verifying-changesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Mr-Quin/danmaku-anywhere --skill verifying-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Mr-Quin/danmaku-anywhere verifying-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mr-Quin/danmaku-anywhere.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/verifying-changes .agents/skills/verifying-changes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verifying-changes" agent skill from https://github.com/Mr-Quin/danmaku-anywhere/tree/master/.claude/skills/verifying-changes into .agents/skills/verifying-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-changes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Mr-Quin/danmaku-anywhere --skill verifying-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Mr-Quin/danmaku-anywhere verifying-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mr-Quin/danmaku-anywhere.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/verifying-changes .cursor/skills/verifying-changes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verifying-changes" agent skill from https://github.com/Mr-Quin/danmaku-anywhere/tree/master/.claude/skills/verifying-changes into .cursor/skills/verifying-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-changes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Mr-Quin/danmaku-anywhere.git --path .claude/skills/verifying-changes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Mr-Quin/danmaku-anywhere --skill verifying-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Mr-Quin/danmaku-anywhere verifying-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mr-Quin/danmaku-anywhere.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/verifying-changes .gemini/skills/verifying-changes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verifying-changes" agent skill from https://github.com/Mr-Quin/danmaku-anywhere/tree/master/.claude/skills/verifying-changes into .gemini/skills/verifying-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-changes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Mr-Quin/danmaku-anywhere verifying-changesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Mr-Quin/danmaku-anywhere --skill verifying-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Mr-Quin/danmaku-anywhere.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/verifying-changes .github/skills/verifying-changes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verifying-changes" agent skill from https://github.com/Mr-Quin/danmaku-anywhere/tree/master/.claude/skills/verifying-changes into .github/skills/verifying-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-changes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Mr-Quin/danmaku-anywhere --skill verifying-changes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Mr-Quin/danmaku-anywhere verifying-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mr-Quin/danmaku-anywhere.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/verifying-changes .opencode/skills/verifying-changes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verifying-changes" agent skill from https://github.com/Mr-Quin/danmaku-anywhere/tree/master/.claude/skills/verifying-changes into .opencode/skills/verifying-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-changes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verifying-changes- GitHub stars
- 547
- Token cost
- ~1.1k tokens
- SKILL.md length
- 578 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Use after changing extension code, to prove it works: which test tier to run, the red-before-green rule, and what to record in the PR test plan.
- Works in 5 steps: Know what you're asserting? → Write the spec as a scratch file under… → Watch it go red against the build… → …
- Tasks that involve End-to-end testing
- SKILL.md covers The loop, Which tier to run, Getting a build without your… and What to record, plus 2 more sections
- Calls pnpm and git
What it does
Verifying Changes is an agent skill from Mr-Quin/danmaku-anywhere. Use after changing extension code, to prove it works: which test tier to run, the red-before-green rule, and what to record in the PR test plan. Start here, then branch to browser-verify or e2e-spec as needed.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering End-to-end testing and Test generation. The repository describes itself as: 一个可以给几乎任何视频网站添加弹幕的开源软件 | An open source solution to add danmaku to almost every video website.
When your agent uses it
- Tasks that involve End-to-end testing
- Tasks that involve Test generation
Example prompts
- “/verifying-changes”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Know what you're asserting?
- Write the spec as a scratch file under e2e/specs/.scratch/ (gitignored, skipped by the
- Watch it go red against the build without your change. A spec that passes both ways
- Make it green, then graduate it: move the file into e2e/specs//.
- Run the right tier (below) and record what you ran.
What it can do on your machine
Read from SKILL.md and the folder at commit d2d6d41. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpmgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Verifying Changes loads about 1.1k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 578 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 578 words (~1,146 tokens).
“The entry point for "I changed something, now show that it works."”
- name
- verifying-changes
Files
Just SKILL.md in .claude/skills/verifying-changes of Mr-Quin/danmaku-anywhere.
Open the folder on GitHubat commit d2d6d41
Compare with similar skills
Verifying Changes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verifying Changes this skillMr-Quin/danmaku-anywhere | 547 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Add E2E Test Suitecrowdin/crowdin-cli | 319 | — | ~2.4k | Automated safety check: Pass | MIT | |
| E2E Test ThinkerUniClipboard/UniClipboard | 1.8k | — | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Migrate E2E To Integrationopenshift/oc-mirror | 124 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Test Scenariosphuryn/pm-skills | 27k | — | ~866 | Automated safety check: Pass | MIT | |
| Memmesh Test IntegrationThinkfleetAI/memmesh | 419 | — | ~621 | Automated safety check: Pass | Apache-2.0 |
Similar skills
E2E Test Thinker
UniClipboard/UniClipboard
Analyze the current branch's diff against main and determine which changes are testable via CLI-based end-to-end tests.
Migrate E2E To Integration
openshift/oc-mirror
Migrate an oc-mirror e2e test case to the integration test suite, translating framework, registry, invocation, and assertion patterns
Test Scenarios
phuryn/pm-skills
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
Memmesh Test Integration
ThinkfleetAI/memmesh
Verify a MemMesh integration produced by memmesh-integrate. An agent skill from ThinkfleetAI/memmesh.
Testing
ItamarZand88/CLI-Anything-WEB
Writes and documents the test suite for a generated cli-web- CLI (Phase 3): unit tests with mocked HTTP, live E2E tests, subprocess tests via resolvecli, and the TEST.md plan/results record.
More from Mr-Quin/danmaku-anywhere
All 9 skills in this repoBabysit PR
Mr-Quin/danmaku-anywhere
A skill your agent uses to monitor an open PR for AI/bot review comments, evaluate them critically, push fixes for real issues, and resolve threads — capped at a sensible duration so it…
Browser Verify
Mr-Quin/danmaku-anywhere
A skill your agent uses when an extension change needs exploration in a real browser — finding selectors, watching a flow, reading console or network.
I18n
Mr-Quin/danmaku-anywhere
A skill your agent uses when adding or changing user-facing strings in the extension (i18n.t calls or locale JSON) under packages/danmaku-anywhere.
Preview Build
Mr-Quin/danmaku-anywhere
A skill your agent uses when you need to load a specific published preview/nightly extension build into the agent's browser by run-number, branch name, or tag.
Reviewing AI Feedback
Mr-Quin/danmaku-anywhere
A skill your agent uses when evaluating review comments from AI reviewers (gemini-code-assist, copilot-pull-request-reviewer) on a PR.
Specs In Clickup
Mr-Quin/danmaku-anywhere
A skill your agent uses when finishing a brainstorm, writing a design spec, or producing an implementation plan in this project.
Related
Categories
Questions about Verifying Changes
What does Verifying Changes do?
Use after changing extension code, to prove it works: which test tier to run, the red-before-green rule, and what to record in the PR test plan. Verifying Changes is an agent skill from Mr-Quin/danmaku-anywhere. Use after changing extension code, to prove it works: which test tier to run, the red-before-green rule, and what to record in the PR test plan.
When should I use Verifying Changes?
Verifying Changes fits situations like: tasks that involve End-to-end testing; tasks that involve Test generation.
How do I install Verifying Changes in Claude Code?
Run `npx skills add Mr-Quin/danmaku-anywhere --skill verifying-changes -a claude-code`. Or copy the skill folder (.claude/skills/verifying-changes in Mr-Quin/danmaku-anywhere) into .claude/skills/verifying-changes in your project. Claude Code loads it when a task matches its description.
How do I install Verifying Changes in Codex?
Run `npx skills add Mr-Quin/danmaku-anywhere --skill verifying-changes -a codex`. Or copy the skill folder (.claude/skills/verifying-changes in Mr-Quin/danmaku-anywhere) into .agents/skills/verifying-changes in your project. Codex loads it when a task matches its description.
Can I use Verifying Changes in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mr-Quin/danmaku-anywhere --skill verifying-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verifying-changes, .gemini/skills/verifying-changes, .github/skills/verifying-changes and .opencode/skills/verifying-changes in your project.
What does Verifying Changes need to run?
Going by SKILL.md and its folder, Verifying Changes needs the command-line tools its instructions call (pnpm and git).
Does Verifying Changes access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Verifying Changes safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Verifying Changes use?
Verifying Changes has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Verifying Changes use?
About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Verifying Changes?
Skills that share tags, products or a category with Verifying Changes: Add E2E Test Suite (crowdin/crowdin-cli, 319 stars), E2E Test Thinker (UniClipboard/UniClipboard, 1.8k stars), Migrate E2E To Integration (openshift/oc-mirror, 124 stars) and Test Scenarios (phuryn/pm-skills, 27k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verifying Changes?
Mr-Quin (a GitHub user) maintains it in Mr-Quin/danmaku-anywhere, which has 547 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on September 7, 2026.
Source: Mr-Quin/danmaku-anywhere on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.