Testing Orcaq
cin12211/orca-q
OrcaQ-specific testing guide. An agent skill from cin12211/orca-q.
Sorts a druxt.js issue by type and package, and reproduces it against the example Drupal backend or with a failing unit test before writing up the findings.
$ npx skills add druxt/druxt.js --skill triage-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install druxt/druxt.js triage-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/druxt/druxt.js.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/triage-issue .claude/skills/triage-issue && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "triage-issue" agent skill from https://github.com/druxt/druxt.js/tree/0.x/.agents/skills/triage-issue into .claude/skills/triage-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/druxt/druxt.js/tree/0.x/.agents/skills/triage-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add druxt/druxt.js --skill triage-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install druxt/druxt.js triage-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/druxt/druxt.js.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/triage-issue .agents/skills/triage-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "triage-issue" agent skill from https://github.com/druxt/druxt.js/tree/0.x/.agents/skills/triage-issue into .agents/skills/triage-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add druxt/druxt.js --skill triage-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install druxt/druxt.js triage-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/druxt/druxt.js.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/triage-issue .cursor/skills/triage-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "triage-issue" agent skill from https://github.com/druxt/druxt.js/tree/0.x/.agents/skills/triage-issue into .cursor/skills/triage-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/druxt/druxt.js.git --path .agents/skills/triage-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add druxt/druxt.js --skill triage-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install druxt/druxt.js triage-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/druxt/druxt.js.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/triage-issue .gemini/skills/triage-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "triage-issue" agent skill from https://github.com/druxt/druxt.js/tree/0.x/.agents/skills/triage-issue into .gemini/skills/triage-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install druxt/druxt.js triage-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add druxt/druxt.js --skill triage-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/druxt/druxt.js.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/triage-issue .github/skills/triage-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "triage-issue" agent skill from https://github.com/druxt/druxt.js/tree/0.x/.agents/skills/triage-issue into .github/skills/triage-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add druxt/druxt.js --skill triage-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install druxt/druxt.js triage-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/druxt/druxt.js.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/triage-issue .opencode/skills/triage-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "triage-issue" agent skill from https://github.com/druxt/druxt.js/tree/0.x/.agents/skills/triage-issue into .opencode/skills/triage-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
triage-issueSorts a druxt.js issue by type and package, and reproduces it against the example Drupal backend or with a failing unit test before writing up the findings.
Triage Issue is an agent skill from druxt/druxt.js. Sorts a druxt.js issue by type and package, and reproduces it against the example Drupal backend or with a failing unit test before writing up the findings. Use when one or more new or unclear druxt.js issues need sorting, reproducing or a next step, or when asked whether a reported bug is real.
Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/tests.yaml`).
It sits in Testing & QA, covering Issue triage and Unit testing. It works with Nuxt. The repository describes itself as: The Fully Decoupled Drupal Framework. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit a225990. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
yarnmakenpmFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
druxtjs.orgFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Triage Issue loads about 763 tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 348 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from druxt/druxt.js at commit a225990, republished under its MIT licence (© druxt). 348 words, ~763 tokens.
.claude/skills/triage-issue/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.The output of triage is a short written report. Labels, milestones and closing issues are for maintainers, so recommend them and leave the change to a maintainer.
Read the issue and its comments. Decide which it is:
druxt, decoupled_router, jsonapi_menu_items or jsonapi_views. Those live on drupal.org, not in this repository.Search open and closed issues for duplicates, and link any you find.
Map the report to a package in packages/, using the package table in AGENTS.md. Note the version the reporter uses and check packages/<package>/CHANGELOG.md for a fix released since. Check that version really has the bug: a bug on develop may not be in any release yet. The version comes from the report, so check it is a plain version number, such as 0.31.0, before it goes into a command. Then npm pack 'druxt-router@0.31.0', quoted and with the real package and version, downloads the published package so you can read its dist/.
Reproduce the bug on develop, in the smallest way available:
A failing unit test in the package's test/ directory, run with yarn build once and then yarn test:unit packages/<package>, since the tests load built packages. This is the best reproduction, because it becomes the regression test.
The example apps against the local Drupal backend:
(cd examples/drupal && make build) # from the repository root
yarn example:druxt-siteThe backend is a minimal Umami site with English and Spanish content. See examples/drupal/.devtools/README.md.
If it does not reproduce, ask for what is missing, such as the Druxt package and Nuxt versions, the Drupal core and module versions, the module configuration in nuxt.config.js, the JSON:API response involved, or a minimal reproduction repository.
Write the triage up in this shape:
**Type:** bug | feature | support | drupal-side
**Package:** druxt-<name> <version>
**Duplicate of:** #<n> (or none found)
**Reproduced:** yes | no | not attempted (steps, or what is missing)
**Likely cause:** <file and line, if found>
**Suggested labels:** <labels>
**Next step:** <a fix and its test, a question for the reporter, or close>Post it on the issue only when the person you work for asks you to. To fix the bug, continue with the start-work skill.
© druxt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in .agents/skills/triage-issue of druxt/druxt.js.
Open the folder on GitHubat commit a225990
Triage Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Triage Issue this skilldruxt/druxt.js | 114 | — | ~763 | Automated safety check: Pass | MIT | |
| Testing Orcaqcin12211/orca-q | 224 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Nuxt Productionsecondsky/claude-skills | 227 | — | ~3.3k | Automated safety check: Notes | MIT | |
| Nuxt Productionsecondsky/claude-skills | 227 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Rust TDD Workflowrtk-ai/rtk | 83k | — | ~753 | Automated safety check: Notes | Apache-2.0 | |
| RTK Filter TDD in Rustrtk-ai/rtk | 83k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 |
cin12211/orca-q
OrcaQ-specific testing guide. An agent skill from cin12211/orca-q.
secondsky/claude-skills
| Nuxt 4 production optimization: hydration, performance, testing with Vitest, deployment to Cloudflare/Vercel/Netlify, and v4 migration.
secondsky/claude-skills
| Nuxt 5 production optimization: hydration, performance, testing with Vitest, deployment to Cloudflare/Vercel/Netlify, and migration from Nuxt 4.
rtk-ai/rtk
Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.
rtk-ai/rtk
Enforces red-green-refactor for new RTK output filters in Rust, using real captured fixtures, snapshot tests with insta and token-savings assertions.
amElnagdy/guard-skills
Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.
druxt/druxt.js
Writes the changeset that versions a druxt.js package change and becomes its changelog entry.
druxt/druxt.js
Works through review comments and failing CI on a druxt.js pull request, fixing or answering each one until the pull request is green and every thread has a reply.
druxt/druxt.js
Prepares and opens a druxt.js pull request from a contributor's fork against develop, with a Conventional Commits title and the repository's template filled in.
druxt/druxt.js
Sets up a druxt.js change before the first edit, from the issue to a feature branch off develop, a short spec and a failing test.
druxt/druxt.js
Runs the druxt.js verification gate (lint, build, unit tests and the checks for whatever else changed) and reports the real results.
druxt/druxt.js
Creates or changes a druxt.js contributor skill in .agents/skills, with its evals and the tests that gate it.
Works with
Categories
Sorts a druxt.js issue by type and package, and reproduces it against the example Drupal backend or with a failing unit test before writing up the findings. js.js issue by type and package, and reproduces it against the example Drupal backend or with a failing unit test before writing up the findings.
Triage Issue fits situations like: unclear druxt.js issues need sorting; asked whether a reported bug is real.
Run `npx skills add druxt/druxt.js --skill triage-issue -a claude-code`. Or copy the skill folder (.agents/skills/triage-issue in druxt/druxt.js) into .claude/skills/triage-issue in your project. Claude Code loads it when a task matches its description.
Run `npx skills add druxt/druxt.js --skill triage-issue -a codex`. Or copy the skill folder (.agents/skills/triage-issue in druxt/druxt.js) into .agents/skills/triage-issue in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add druxt/druxt.js --skill triage-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage-issue, .gemini/skills/triage-issue, .github/skills/triage-issue and .opencode/skills/triage-issue in your project.
Going by SKILL.md and its folder, Triage Issue needs the command-line tools its instructions call (yarn, make and npm).
SKILL.md names 1 domain. As links in the text: druxtjs.org. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Triage Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 763 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Triage Issue: Testing Orcaq (cin12211/orca-q, 224 stars), Nuxt Production (secondsky/claude-skills, 227 stars), Nuxt Production (secondsky/claude-skills, 227 stars) and Rust TDD Workflow (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
druxt (a GitHub organization) maintains it in druxt/druxt.js, which has 114 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.
Source: druxt/druxt.js on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.