embedded-coverage-strategy-reference SKILL.md skillA
embedded-coverage-strategy-reference from testland/qa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testland/qa/embedded-coverage-strategy-reference@v1.3.8Pins v1.3.8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testland/qa
- Path
plugins/qa-embedded/skills/embedded-coverage-strategy-reference/SKILL.md- Versions recorded
- 5
- Latest version
- v1.3.8, committed Oct 11, 2026
- First version recorded
- Jul 19, 2026
- Size
- 15,093 bytes
- Repository stars
- 11
- License
- MIT
Pure-reference catalog of code-coverage strategy for embedded C/C++: the criteria hierarchy (statement / branch / decision / condition / MC/DC), the gcov toolchain (.gcno/.gcda, --coverage), the LLVM source-based toolchain (llvm-profdata / llvm-cov), host-build vs QEMU-build instrumentation, MISRA-C:2012 and DO-178C structural-coverage expectations by safety level (DAL A maps to MC/DC), and report-format choices. Use when choosing what structural-coverage level to require and wiring gcov /…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# embedded-coverage-strategy-reference ## Overview This skill is a **pure reference** consumed by the per-tool skills (`googletest-embedded-arm`, `unity-test-framework-c`, `ceedling-build-runner`, `qemu-system-test-runner`) and by the HIL reference (`hardware-in-loop-reference`). ## When to use - Choosing a coverage criterion for a new embedded test suite - what does "enough coverage" mean for this project? - Wiring gcov or llvm-cov into the cross-compile build. - Reading a coverage report and translating between gcov, LCOV, and llvm-cov formats. - Negotiating coverage requirements against a safety standard (MISRA-C, DO-178C, ISO 26262, IEC 62304). - Deciding whether to instrument the host build, the QEMU build, or the on-target build. ## How to use 1. Pick the coverage **criterion** the project's safety level demands (DAL A / ASIL D map to MC/DC; DAL B to decision; DAL C / ASIL A to statement) from the criteria hierarchy - full standards mapping in [references/safety-standards-and-formats.md](references/safety-standards-and-formats.md). …
Read the whole file at its exact version.
How to install
mdr add testland/qa/embedded-coverage-strategy-reference@sha256:9311720df6f35d8bThe line at the top of this page pins the label v1.3.8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_25ngajrm7qi4dzcs)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 19, 2026 and Oct 11, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.3.8 latest | 2026-10-11 | a1bd3f7 | 15,093 B | A | view · diff |
| git:20260726.8b2e4a2 | 2026-07-26 | 8b2e4a2 | 15,074 B | A | view · diff |
| git:20260725.09af35b | 2026-07-25 | 09af35b | 15,330 B | A | view · diff |
| git:20260724.d4db756 | 2026-07-24 | d4db756 | 14,894 B | A | view · diff |
| git:20260719.6226ac1 | 2026-07-19 | 6226ac1 | 15,128 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15093 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_25ngajrm7qi4dzcs GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/embedded-coverage-strategy-reference GET https://markdownregistry.com/api/v1/blob/9311720df6f35d8bc1d3226b02db9f65e14327f7661b970633582bd107c576f9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.