agentleFS
gpambroziogpambrozio/Gallager/.claude/skills/e2e-for-feature/SKILL.md

e2e-for-feature

Skill4 starsChanged 57 days agoAGPL-3.0View on GitHub

Automatically create E2E test scenarios that prove a new feature works. Use this skill when a PR or branch introduces a new feature and you want to generate an end-to-end scenario that exercises it, takes screenshots at key points, and verifies the screenshots show the expected behavior. Trigger when: the user says "create e2e for this feature", "write an e2e test for this PR", "prove this feature works with e2e", "add e2e coverage for this change", or any variation of wanting automated E2E proof that new code works. Also use when the user asks to "test this feature end to end" or "create a scenario for the new feature". Do NOT use for fixing existing failing scenarios (use e2e-testing), manual debugging (use e2e-manual-debugging), or reviewing baselines (use baseline-review).

  • Deletes or force-pushes

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 13 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.