Other AI coding assistants
Set up Doc Detective agent tools with any AI coding assistant that supports Agent Skills.
Doc Detective agent tools work with Codex, Cursor, OpenCode, Qwen Code, and other assistants. If your assistant supports skills, extensions, or plugins, you can likely use these tools.
Installation
npx doc-detective install-agents supports three of the agents on this page directly. Fallback procedures for the rest appear further down.
Codex:
Without --scope, the CLI prompts for which scope to use.
The command fetches doc-detective’s skills from GitHub and copies them into the user’s (or project’s) .agents/skills/ directory. Codex auto-discovers skills on its next launch.
Qwen Code:
The command invokes qwen extensions install non-interactively to add the doc-detective extension with auto-update enabled. Qwen Code installs extensions user-globally only, so the --scope flag has no effect for this agent.
OpenCode:
Without --scope, the CLI prompts for which scope to use.
The command fetches the agent-tools bundle and copies skills, the runtime plugin, hooks, and agents into the appropriate scope directory (~/.config/opencode/ or ./.opencode/). OpenCode auto-discovers them on next launch.
All three installs are idempotent: re-running prints already up to date when nothing has changed. Use --force to reinstall regardless. Use --dry-run to preview actions without executing them.
Fallback procedures
Use these if npx doc-detective install-agents isn’t an option for your workflow, or for agents that the command doesn’t support directly (for example, Cursor).
Install with npx skills
The skills package from Vercel provides a quick way to install skills for multiple AI tools:
Follow the prompts. The CLI auto-detects which AI tools you have installed and places the skills in the appropriate directories.
Manual installation
Clone the repository and copy the skills to your agent’s configuration directory:
Replace .{agent-dir} with your agent’s expected skill/plugin directory. Common directories include:
Check your assistant’s documentation for the correct directory if yours isn’t listed.
Bootstrap a project
Set up Doc Detective in your repository using a slash command (if your assistant supports them):
Or describe what you want in plain language:
Set up Doc Detective in this project. Scan for documentation files, create a config, and generate tests for any procedures you find.
The bootstrapping process:
- Detects documentation files (
.md,.mdx,.adoc,.rst,.html,.dita) - Generates a
.doc-detective.jsonconfiguration file - Creates test specifications for procedures with step-by-step instructions
- Runs the tests and fixes failures
Generate tests for existing pages
Convert a documentation file into a test specification using a slash command:
Or ask in plain language:
Generate Doc Detective tests for the getting started guide. Save the output to a JSON file in the tests folder.
You can also ask for more specific behavior:
Create tests for docs/new-feature.md and merge them with the existing test spec in tests/existing-spec.json.