SkillsAdd

wordbricks/onequery · Archived

onequery-bug

Diagnose GitHub bug reports in wordbricks/onequery.

Installation

$ npx skills add wordbricks/onequery --skill onequery-bug
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

xstate Same source
wordbricks/onequery

Design, implement, and review XState v5 state machines and @xstate/react integrations in TypeSc…

0 installs
tanstack-router-best-practices Same source
wordbricks/onequery

TanStack Router best practices for type-safe routing, data loading, search params, and navigati…

0 installs
tanstack-query-best-practices Same source
wordbricks/onequery

TanStack Query (React Query) best practices for data fetching, caching, mutations, and server s…

0 installs
react-no-use-effect Same source
wordbricks/onequery

Enforce the no-useEffect rule when writing or reviewing React code. Activate when writing React…

0 installs

Also in this package

Other skills from wordbricks/onequery · top by installs.

npx skills add wordbricks/onequery
xstate 0 tanstack-router-best-practices 0 tanstack-query-best-practices 0 react-no-use-effect 0 protobuf 0 onequery-pr-body 0 onequery-blog-images 0 knip-deadcode 0 gh-pr-writing 0 drizzle-migration-conflict-resolution 0

Browse all from wordbricks/onequery

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 17
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,617 B
  • docs SUMMARY.md 304 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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

  1. 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.
  1. 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

  • 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.
  1. 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.
  1. 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.
  1. 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).
  1. Respond
  • Provide a concise report of your findings and next steps.