reproduce-bug
Skill14 starsChanged 3 months agoMITView on GitHub
Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Reproduce Bug”. A useful skill states the six fields from Skills and routines. A bug report must become a reproduction pack in staging with steps, expected vs actual, environment, and evidence — not a guess in the comments. Steps are numbered and were actually performed. Screenshots match the claimed actual. No production customer data was used. Repro pack: environment, steps, expected,…
5 other projects use a version of this.
Adopted by
Most recently taken up by
- kaiohenricunha/dotbabeltheir own version, first seen Oct 17, 2026
- googleapis/mcp-toolboxtheir own version, first seen Oct 8, 2026
- googleapis/genai-toolboxtheir own version, first seen Oct 8, 2026
- TriunaLabs/skillstheir own version, first seen Sep 30, 2026
- MarkTripoli/skillstheir own version, first seen Sep 25, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- googleapis/mcp-toolbox★ 17ksame name
- googleapis/genai-toolbox★ 17ksame name
- MarkTripoli/skills★ 2same name
- kaiohenricunha/dotbabel★ 0same name
- TriunaLabs/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- convert/claude.mdCLAUDE.md
- docs/llms.txtllms.txt
- audit-subscriptionsSkill
- cited-researchSkill
- cloud-bill-noteSkill
- collate-feature-asksSkill
- coordinate-launchSkill
- daily-digestSkill
- defend-calendarSkill
- design-bot-templateSkill
- detect-docs-driftSkill
- diff-competitorsSkill
- draft-call-followupSkill
- draft-changelogSkill
- draft-issueSkill
- draft-newsletterSkill
- draft-security-answersSkill
- draft-sqlSkill
- draft-support-replySkill
- garden-memorySkill
- harden-repoSkill
- incident-timelineSkill
- install-teamSkill
- interrogate-assumptionsSkill
- investigate-perfSkill
- log-promisesSkill
- package-evidenceSkill
- plan-tripSkill
- prep-meetingSkill
- queue-socialSkill
- ramp-new-hireSkill
- rank-account-healthSkill
- recommend-media-reallocSkill
- reconcile-expensesSkill
- remix-contentSkill
- research-accountsSkill
- review-pr-riskSkill
- route-workSkill
- sanitize-shareSkill
- scout-x-threadsSkill
- source-talentSkill
- sweep-ciSkill
- triage-inboxSkill
- vendor-renewalsSkill
- watch-aeoSkill
- watch-brandSkill
- weekly-saas-financeSkill
- write-win-lossSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
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
- Distinctive: line 22
Read the report. List what is actually specified vs guessed.
- Distinctive: line 25
If you cannot reproduce, write the attempts and stop.
- Distinctive: line 39
Do not use production data.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Reproduce Bug
Paste this into Grok Bot after a successful run:
Save the process we just used as a skill called “Reproduce Bug”.
A useful skill states the six fields from Skills and routines.
1. When to use it
A bug report must become a reproduction pack in staging with steps, expected vs actual, environment, and evidence — not a guess in the comments.
2. Required inputs and access
- Bug report or ticket
- Staging URL and approved test credentials via secure handoff (never chat)
- Browser and OS constraints if the report named them
3. Sequence of work
- Read the report. List what is actually specified vs guessed.
- Reproduce in staging with a fresh test account. Never production customer data.
- Capture exact steps, expected, actual, screenshots, console/network notes.
- If you cannot reproduce, write the attempts and stop. Do not close the ticket.
4. How to validate the result
Steps are numbered and were actually performed. Screenshots match the claimed actual. No production customer data was used.
5. What to return
Repro pack: environment, steps, expected, actual, evidence, minimal test case or "could not reproduce".
6. What requires approval
Do not use production data. Do not change production settings. Do not file the GitHub issue unless asked — hand that to issue-drafter.
Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.
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.