How do I install the Verify Pr skill?

Run npx skillmds@latest add duckduckgo/verify-pr 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 Verify Pr 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 Verify Pr?

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 Verify Pr free to use?

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

Who published Verify Pr?

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

Verify Pr by duckduckgo — Agent Skill

Name: Verify Pr
Author: duckduckgo

Verify Pr

Verifies an autoconsent pull request by running local CI checks, reviewing rule quality, and inspecting Jenkins E2E results. Use when reviewing, verifying, or approving a PR, when checking if a PR is ready to merge, or when the user asks to validate PR changes.

duckduckgo d77f9bb 2.4 KB Updated Sep 17, 2026

File contents

Verify PR

Copy this checklist and track progress:

PR Verification:
- [ ] Step 1: Local checks pass
- [ ] Step 2: Rule review complete
- [ ] Step 3: CI results checked
- [ ] Step 4: Browser verification done

Step 1: Local Checks

npm run lint
npm run rule-syntax-check
npm run test:lib
npx playwright test tests/<cmp>.spec.ts --project webkit

If any check fails, fix the issue and re-run before proceeding.

Step 2: Rule Review

JSON rule PRs

Test spec exists in tests/ with reachable URLs
Selectors are stable (no CSS module hashes, dynamic IDs, or framework-generated IDs)
optOut targets a reject/decline button, not a privacy policy link or close button
prehideSelectors are narrow (no body or full-page selectors)
minimumRuleStepVersion: 2 if rule uses removeClass, setStyle, or addStyle
Generated rule fixes (rules/generated/) are consistent across all region variants

Code-based rule PRs

No hardcoded site-specific values
Fallback paths for regional variants
Uses existing DOM helpers (this.click(), this.waitForElement(), etc.)

Step 3: CI Results

GitHub Actions (.github/workflows/checks.yml): Runs lint and test:lib. Must pass.

Jenkins: Runs Playwright E2E in 9 regions (US, GB, AU, CA, DE, FR, NL, CH, NO) for modified rules only. Posts a PR comment with artifact ZIP and review tool link for inspecting screenshots.

Flaky E2E failures

Before concluding a test is broken:

Check Jenkins screenshots in the review tool
Verify the site still shows the same popup
Region-only failures → consider adding skipRegions
CI retries twice — intermittent failures often self-resolve

Step 4: Browser Verification

Build and load extension: npm run prepublish → load dist/addon-mv3/ in Chrome.

Confirm on target site(s):

Popup is detected and handled
Page scrolls normally after opt-out
Interactive elements remain clickable

For CMP rules: test on multiple sites using the same CMP (find sites in data/coverage.json).

---name: verify-prdescription: Verifies an autoconsent pull request by running local CI checks, reviewing rule quality, and inspecting Jenkins E2E results. Use when reviewing, verifying, or approving a PR, when checking if a PR is ready to merge, or when the user asks to validate PR changes.---# Verify PRCopy this checklist and track progress:```PR Verification:- [ ] Step 1: Local checks pass- [ ] Step 2: Rule review complete- [ ] Step 3: CI results checked- [ ] Step 4: Browser verification done```## Step 1: Local Checks```bashnpm run lintnpm run rule-syntax-checknpm run test:libnpx playwright test tests/<cmp>.spec.ts --project webkit```If any check fails, fix the issue and re-run before proceeding.## Step 2: Rule Review### JSON rule PRs- [ ] Test spec exists in `tests/` with reachable URLs- [ ] Selectors are stable (no CSS module hashes, dynamic IDs, or framework-generated IDs)- [ ] `optOut` targets a reject/decline button, not a privacy policy link or close button- [ ] `prehideSelectors` are narrow (no `body` or full-page selectors)- [ ] `minimumRuleStepVersion: 2` if rule uses `removeClass`, `setStyle`, or `addStyle`- [ ] Generated rule fixes (`rules/generated/`) are consistent across all region variants### Code-based rule PRs- [ ] No hardcoded site-specific values- [ ] Fallback paths for regional variants- [ ] Uses existing DOM helpers (`this.click()`, `this.waitForElement()`, etc.)## Step 3: CI Results**GitHub Actions** (`.github/workflows/checks.yml`): Runs `lint` and `test:lib`. Must pass.**Jenkins**: Runs Playwright E2E in 9 regions (US, GB, AU, CA, DE, FR, NL, CH, NO) for modified rules only. Posts a PR comment with artifact ZIP and [review tool](https://zok.pw/autoconsent-review-tool/) link for inspecting screenshots.### Flaky E2E failuresBefore concluding a test is broken:1. Check Jenkins screenshots in the review tool2. Verify the site still shows the same popup3. Region-only failures → consider adding `skipRegions`4. CI retries twice — intermittent failures often self-resolve## Step 4: Browser VerificationBuild and load extension: `npm run prepublish` → load `dist/addon-mv3/` in Chrome.Confirm on target site(s):- Popup is detected and handled- Page scrolls normally after opt-out- Interactive elements remain clickableFor CMP rules: test on multiple sites using the same CMP (find sites in `data/coverage.json`).

Frequently asked questions