agentleFS
Sign inStart free
forcedotcomforcedotcom/salesforcedx-vscode/.cursor/skills/manual-test-plan-judgment/SKILL.md

manual-test-plan-judgment

Skill1k starsChanged 25 days agoBSD-3-ClauseView on GitHub

Manual test plan JSON for one PR. Only caller is the manual test plan script.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about forcedotcom/salesforcedx-vscode

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on GitHub and Stack Overflow (52 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the diff and the code.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Manual test plan judgment

Read the diff and the code. Reply with one JSON object. No other text. No fences.

{ "kind": "nothing" } when no extension surface (CI, docs, types-only, tooling), or every changed surface is already asserted.

{ "kind": "checklist", "items": [ ... ] } with 1+ items:

  • { "kind": "watch-video", "spec": "<path>", "workflow": "<workflow name>", "job": "<job key>" }
  • { "kind": "manual", "step": "<what to look at>" }

spec: repo-relative path, test/playwright then a .spec.ts file that exists. workflow: name: of a leaf *E2E.yml. Not e2e.yml, playwrightE2EFullSuite.yml, rerunPushE2E.yml. job: one job key in that file. Not a union such as e2e-web | e2e-desktop.

Trace the end-user change. A services or language-server diff still counts when a user can see it. Language servers are on-screen.

An assertion clears only what it asserts. Command-exists, UI-opened, and no-critical-errors do not clear a surface.

manual when e2e does not assert the surface, including refactors. No artifact URL.

A watch-video item that fails those checks is rejected. The script sends the error back once.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free