pre-push-e2e
Skill0 starsChanged 5 months agoNo licenceView on GitHub
PRE-PUSH gate: automatically generates a Cypress E2E spec before an engineer pushes their branch. Triggers when: engineer says 'done', 'selesai', 'beres', 'siap push', 'mau push', 'ready to push', 'before push', 'mau commit', 'mau PR', 'buatin test dulu', 'generate test'; or when a feature/fix/update has just been completed and no E2E spec exists for the ticket yet. Reads git diff to understand what changed, extracts ticket ID from branch name, fetches Jira ticket for context, reads changed source files to identify routes/APIs/UI, then generates a complete Cypress E2E spec following ASTRNT conventions: export {} header, JSDoc coverage block, constants, stubApis helper, loginAndVisit helper, describe/it blocks covering happy path + empty state + API error state.
- Reads credentials
In this repository8 other files it gives its agents.
- be-db-engineerSkill
- browser-actSkill
- create-prd-ducSkill
- cypress-authorSkill
- cypress-docsSkill
- cypress-explainSkill
- fe-ux-engineerSkill
- resolve-conflictSkill
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.
No licence file, so all rights are reserved — 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 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.
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.