handling-flaky-changes
Skill0 starsChanged 9 days agoMITView on GitHub
Handles flaky or known visual changes in SnapVisor: ignores or un-ignores a change after confirmation, finds flaky tests, and lists the ignored changes for a project. Use when the user asks to 'ignore the date-widget change, it's the flaky clock again', 'which tests are flaky', 'stop flagging this change', 'un-ignore this change', 'show ignored changes', or deal with noisy screenshot diffs.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- booking-meetingsSkill
- building-onboarding-workflowsSkill
- building-study-guidesSkill
- capturing-tasksSkill
- capturing-web-pagesSkill
- chasing-unpaid-invoicesSkill
- checking-domain-connectionsSkill
- checking-email-deliverabilitySkill
- checking-notification-deliverySkill
- checking-uptime-statusSkill
- cleaning-up-bookkeepingSkill
- connecting-customer-domainsSkill
- discussing-buildsSkill
- drafting-invoicesSkill
- drafting-social-postsSkill
- editing-demosSkill
- editing-page-draftsSkill
- extracting-document-textSkill
- finding-meeting-timesSkill
- investigating-tasksSkill
- making-demo-videosSkill
- managing-bookingsSkill
- managing-content-calendarSkill
- managing-demosSkill
- managing-voice-librarySkill
- planning-revisionSkill
- preflighting-domainsSkill
- publishing-pagesSkill
- reading-financial-reportsSkill
- reading-text-aloudSkill
- reading-web-pagesSkill
- reporting-snapvisor-usageSkill
- researching-course-materialSkill
- researching-summary-librarySkill
- responding-to-incidentsSkill
- reviewing-email-performanceSkill
- reviewing-notification-workflowsSkill
- reviewing-social-performanceSkill
- reviewing-visual-buildsSkill
- reviewing-workloadSkill
- searching-getitdone-api-docsSkill
- sending-email-campaignsSkill
- sending-notificationsSkill
- setup-bioflowSkill
- setup-calySkill
- setup-demofySkill
- setup-dodomainSkill
- setup-getitdoneSkill
- setup-notiflySkill
- setup-postifySkill
- setup-sendlySkill
- setup-shortySkill
- setup-snapvisorSkill
- setup-superbooksSkill
- setup-unotesSkill
- setup-upapiSkill
- setup-uptimelySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Operations listed by name: call them directly, for example snapvisor:listBuilds.
- Very specific: line 24
If the connection lists the operations by name instead (the per-tool surface), call them directly without the external_ prefix.
- Very specific: line 38
Before ignoring, fetch external_getTest for that diff's test with metricsPeriod: "LAST_30_DAYS" so the user sees whether it really flakes.
- Very specific: line 56
Check the real field names in the snapvisor:search_tools declarations before relying on them.
- Very specific: line 61
Do not approve or reject builds from this skill.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated from plugins/snapvisor/skills/handling-flaky-changes/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Flaky and ignored changes in SnapVisor
Silence a single known-noisy change so it stops blocking a build, undo that when needed, and show which tests flake most. Ignoring affects one change; every other diff in the build stays as it is.
Connecting and calling the tools
Every operation in this skill comes from the snapvisor MCP server, the SnapVisor connector. The server defaults to Code Mode, so the operations below are written as the external_* functions you call inside snapvisor:execute_typescript. On a server set to the per-tool surface, the same operation is listed as snapvisor:<name> without the external_ prefix, for example snapvisor:listBuilds.
- Only
snapvisor:search_toolsandsnapvisor:execute_typescriptlisted (Code Mode, the default): callsnapvisor:search_toolsfirst, then call each tool insidesnapvisor:execute_typescriptasexternal_<tool>(for exampleexternal_listBuilds); the program mustreturnits result. Scopes, confirmations and gates are identical on both surfaces. - Operations listed by name: call them directly, for example
snapvisor:listBuilds. - "Tool not found": switch to the Code Mode route instead of retrying the direct call. If
snapvisor:search_toolsdoes not return the tool either, its OAuth scope was not granted; the user reconnects SnapVisor and approves that scope. - No
snapvisortools at all: SnapVisor is not connected yet. Follow thesetup-snapvisorskill.
Tools you will use
The snapvisor MCP server has two tools: snapvisor:search_tools (find operations and their inputs; call it first, for example with change, test, ignore) and snapvisor:execute_typescript (run a short program calling the declared external_* functions, which are already in scope; the program must return its result).
If the connection lists the operations by name instead (the per-tool surface), call them directly without the external_ prefix.
Operations this skill uses (confirm with snapvisor:search_tools):
external_listBuildDiffs: diffs in a build; each carries itstestand itschange, whose id is what the ignore operations take.external_ignoreChangeandexternal_unignoreChange: mark one change ignored or restore it, bychangeId.external_listTests: tests in a project.external_getTest: one test with its flakiness metrics for ametricsPeriod(LAST_24_HOURSup toLAST_90_DAYS).external_listTestChanges: a test's changes; filter withignored.external_listIgnoredChanges: changes currently ignored in a project.
Workflow
- Identify the build and the change the user means. Call
external_listBuildDiffsand match on the screenshotname. If more than one diff matches, list them and ask which one. - Before ignoring, fetch
external_getTestfor that diff's test withmetricsPeriod: "LAST_30_DAYS"so the user sees whether it really flakes. - Confirm: "Ignore the change on
checkout/date-widgetin build 42?" On a yes, callexternal_ignoreChangewith the change id and report the result. - To un-ignore, find the change with
external_listIgnoredChangesorexternal_listTestChangeswithignored: "true", confirm, then callexternal_unignoreChange. - For "which tests are flaky", list the project's tests, fetch
external_getTestfor them in one program withawait Promise.all, and return them sorted by their flakiness metric. Report the top ones with their numbers.
Code Mode pattern
const tests = await external_listTests({ owner, project });
const detail = await Promise.all(
tests.results.slice(0, 25).map((t) =>
external_getTest({ owner, project, testId: t.id, metricsPeriod: "LAST_30_DAYS" })
.catch((e) => ({ id: t.id, error: String(e) })),
),
);
return detail;Check the real field names in the snapvisor:search_tools declarations before relying on them. Errors read <CODE>: <details>.
Rules
- Ignore one change at a time, each after a confirmation. Never ignore every diff in a build to make it pass.
- Do not approve or reject builds from this skill; hand off to
reviewing-visual-builds. - Report only metrics the operations returned. If a test has no flakiness data for the period, say so.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

