CI / PowerShell tests on Ubuntu (push) Failing after 3s
CI / CI configuration security checks (push) Successful in 4s
CI / Capabilities and shell quality (push) Successful in 22s
CI / Python tests and compilation (push) Successful in 23s
CI / Build and inspect generated packages (push) Successful in 19s
CI / Bash integration and installation guards (push) Failing after 22s
CI / Installed client configuration smoke tests (push) Successful in 1m16s
CI / QMD local search integration (push) Failing after 12m46s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
name, description
| name | description |
|---|---|
| technical-research | MUST use before relying on an external library, API, tool, product version, or standard whose current behavior you have not verified in this session, and before choosing between technical options. Prefer primary sources. Not for repository code discovery (use repository-research). |
Technical Research
Verify external technology before it shapes the solution. Do not rely on remembered API signatures, defaults, or version behavior when they could have changed.
Workflow
- Turn the question into specific facts or decisions that need evidence. When the question concerns how this repository already uses the technology, run
repository-researchfirst and research only what the code does not answer. - Prefer current primary sources: official documentation, standards, release notes, or source code of the exact version in use. Check version and date when behavior may have changed.
- Compare only viable options against the user's constraints, compatibility needs, security properties, and maintenance cost.
- Separate source-backed facts from interpretation. Record assumptions and any material evidence that is missing or conflicting.
- Recommend an option only when evidence supports it. Explain the deciding trade-off briefly.
Return concise findings with direct sources and an implementation-relevant conclusion. Do not implement the change.