Use OrangePro to find behavioral test gaps and generate grounded tests for this repository.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add OrangeproAI/orangepro-mcp --skill opro --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Opro?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/orangeproai-opro)More formats (shields.io, HTML) on the badges page.
---
name: opro
description: Use OrangePro to find behavioral test gaps and generate grounded tests for this repository.
---
Use the OrangePro MCP tools for local evidence-graph analysis and grounded test generation.
1. Start with `orangepro_start` for the current checkout.
2. If OrangePro reports a large-repo scope breakdown, prefer a focused scope for AI/generation; full deterministic analysis is still allowed.
3. For PR work, call `orangepro_generate_tests` with `base_ref=main`.
4. For baseline work, call `orangepro_find_test_gaps`, pick one high-priority gap, then call `orangepro_generate_tests` for that target.
5. Write only generated tests that include `run_hints`; drafts are context, not runnable claims.
6. Run the suggested command from the owning package directory.
7. After a pass, call the returned `prove_run` args so OrangePro can dynamically prove the target. Use `record_run` only for static diagnostics.
8. Report status as Proven, Reproven, Runtime-covered, Associated signal, or No link. Never promote Associated signal or AI links to Proven.
OrangePro may use weak AI grounding when a provider key is configured, but AI links are suggestions for generation only and never change Proven coverage.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Practical guide to testing web applications with screen readers for comprehensive accessibility validation.
Plan a weekly editorial calendar by mapping company goals to publishable topics, owners, status, and verification notes.
Run, verify, reseed, and repair Paperclip isolated dev workspace services. Use when asked to start or fix a managed project/worktree service and prove health, login readiness, cloned data, runtime visibility, and correct port ownership.
Prepare a Paperclip branch for PR with commits, template body, and checks.
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
