duroxide-code-coverage Skill
Measure and improve code coverage in the Duroxide durable execution runtime. Use when asked about coverage, testing coverage, running llvm-cov, or improving test coverage percentages. Published by microsoft in duroxide.
Decision snapshot
Is this a fit?
Browser automation, Testing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is duroxide-code-coverage Skill?
Measure and improve code coverage in the Duroxide durable execution runtime. Use when asked about coverage, testing coverage, running llvm-cov, or improving test coverage percentages. Published by microsoft in duroxide. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Testing
- Browser automation use cases
- Testing use cases
Declared skill metadata
- Declared author: duroxide
- Declared license: Apache-2.0
- Source file: .github/skills/duroxide-code-coverage/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use duroxide-code-coverage Skill
- Use it for browser automation.
- Use it for testing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/duroxide
- Skill file: .github/skills/duroxide-code-coverage/SKILL.md
What it does
Measure and improve code coverage in the Duroxide durable execution runtime. Use when asked about coverage, testing coverage, running llvm-cov, or improving test coverage percentages.
Skill instructions
Duroxide Code Coverage Guidance for measuring and improving code coverage in the Duroxide codebase. Quick Commands bash Summary (recommended for quick checks) cargo llvm-cov nextest -p duroxide --all-features --summary-only Detailed per-file report cargo llvm-cov nextest -p duroxide --all-features HTML report (opens in browser) cargo llvm-cov nextest -p duroxide --all-features --html --open Install llvm-cov if needed cargo install cargo-llvm-cov Coverage Targets | Metric | Target | Notes | |--------|--------|-------| | Lines | 90% | Primary metric | | Regions | 85% | Branch coverage | | Functions | 80% | Often lower due to unused helpers | Priority Files When coverage drops, focus on these files: 1. src/providers/error.rs - Target 100%, error classification 2. src/runtime/observability.rs - Target 90%, metrics correctness 3. src/providers/sqlite.rs - Target 85%, reference implementation 4. src/providers/instrumented.rs - Target 75%, observability wrapper 5. src/providers/management.rs
Verified compatibility and discovery
Frequently asked questions
What is duroxide-code-coverage?
duroxide-code-coverage is a open-source AI agent skill with Copy skill directory. Measure and improve code coverage in the Duroxide durable execution runtime. Use when asked about coverage, testing coverage, running llvm-cov, or improving test coverage percentages.
Who is duroxide-code-coverage best for?
duroxide-code-coverage is best for reusing agent instructions, scripts, and references, browser automation workflows, testing workflows.
How do I install duroxide-code-coverage?
Install or run duroxide-code-coverage using Copy skill directory. Check duroxide-code-coverage for the latest setup command.
Is duroxide-code-coverage actively maintained?
duroxide-code-coverage may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
