onequery-bug
Skill17 starsChanged 6 months agoApache-2.0View on GitHub
Diagnose GitHub bug reports in wordbricks/onequery. Use when given a GitHub issue URL from wordbricks/onequery and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-browserSkill
- agentic-legibilitySkill
- babysit-prSkill
- better-result-adoptSkill
- code-breaking-changesSkill
- code-review-change-sizeSkill
- code-reviewSkill
- code-review-testingSkill
- drizzle-migration-conflict-resolutionSkill
- gh-pr-writingSkill
- knip-deadcodeSkill
- onequery-blog-imagesSkill
- onequery-pr-bodySkill
- protobufSkill
- react-no-use-effectSkill
- tanstack-query-best-practicesSkill
- tanstack-router-best-practicesSkill
- xstateSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
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
- Distinctive: line 17
If the URL is missing or not in the right repo, ask the user for the correct link.
- Distinctive: line 21
Always access the issue over the network immediately, even if you think access is blocked or unavailable.
- Distinctive: line 22
Prefer the GitHub API over HTML pages because the HTML is noisy:
- Distinctive: line 25
If the environment requires explicit approval, request it on demand via the tool and continue without additional user prompting.
- Distinctive: line 26
Only if the network attempt fails after requesting approval, explain what you can do offline (e.g., draft a response template) and ask how …
- Distinctive: line 30
Use the GitHub API responses (issue + comments) as the source of truth rather than scraping the HTML issue page.
- Distinctive: line 33
If the report includes a thread ID, mention it in the summary and use it to look up the logs and session details if you have access to them.
- Distinctive: line 37
Before inspecting code, docs, or logs in depth, write a short summary of the report in your own words.
- Distinctive: line 42
Verify with sources: when the report is specific and likely reproducible.
- Distinctive: line 43
Request more information: when the report is vague, missing repro steps, or lacks logs/environment.
- Distinctive: line 44
Explain not a bug: when the report contradicts current behavior or documented constraints (cite the evidence from the issue and any local …
≈ “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.
Files
OneQuery Bug
Overview
Diagnose a OneQuery GitHub bug report and decide the next action: verify against sources, request more info, or explain why it is not a bug.
Workflow
- Confirm the input
- Require a GitHub issue URL that points to
github.com/wordbricks/onequery/issues/…. - If the URL is missing or not in the right repo, ask the user for the correct link.
- Network access
- Always access the issue over the network immediately, even if you think access is blocked or unavailable.
- Prefer the GitHub API over HTML pages because the HTML is noisy:
- Issue:
https://api.github.com/repos/wordbricks/onequery/issues/<number> - Comments:
https://api.github.com/repos/wordbricks/onequery/issues/<number>/comments
- Issue:
- If the environment requires explicit approval, request it on demand via the tool and continue without additional user prompting.
- Only if the network attempt fails after requesting approval, explain what you can do offline (e.g., draft a response template) and ask how to proceed.
- Read the issue
- Use the GitHub API responses (issue + comments) as the source of truth rather than scraping the HTML issue page.
- Extract: title, body, repro steps, expected vs actual, environment, logs, and any attachments.
- Note whether the report already includes logs or session details.
- If the report includes a thread ID, mention it in the summary and use it to look up the logs and session details if you have access to them.
- Summarize the bug before investigating
- Before inspecting code, docs, or logs in depth, write a short summary of the report in your own words.
- Include the reported behavior, expected behavior, repro steps, environment, and what evidence is already attached or missing.
- Decide the course of action
- Verify with sources when the report is specific and likely reproducible. Inspect relevant Codex files (or mention the files to inspect if access is unavailable).
- Request more information when the report is vague, missing repro steps, or lacks logs/environment.
- Explain not a bug when the report contradicts current behavior or documented constraints (cite the evidence from the issue and any local sources you checked).
- Respond
- Provide a concise report of your findings and next steps.
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.