agentleFS
mystilleefmystilleef/spae-framework/skills/coverage/SKILL.md

coverage

Skill2 starsChanged 14 days agoMITView on GitHub

Orchestrates test agents sequentially to cover behavioral gaps.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use scan, lint and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • rajnavakotiSkill

    scan

    Run the AI dashboard scanner and generate the HTML report.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    lint

    Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.

    Also in 4 projects that use this

  • julienamorganSkill

    profile

    Researches the user's market, competitors, and competitive positioning to build a complete ICP profile. Shows findings for user approval before proceeding. Triggers: /profile, "research my market", "who are my competitors". Reads: ./gtm/company.md, ./gtm/icp.md. Writes: updates ./gtm/icp.md with competitive positioning. Standalone: yes (asks for domain if company.md missing).

    Also in 3 projects that use this

  • asterkinSkill

    adr

    Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.

    Also in 4 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

  • MicrosoftSkill

    worktree

    Create, reuse or clean up a dedicated git worktree for working on a pull request or a private branch. Use from any PR-scoped workflow that needs an isolated checkout to keep current code and build output untouched.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run test subagents sequentially to cover behavioral gaps in target code.

    line 18
  2. Distinctive:

    Always use the subagent tool for subagent invocation.

    line 41
  3. Distinctive:

    Never run subagents in parallel or concurrently.

    line 52
  4. Distinctive:

    Every run, halted or not, ended in Report.

    line 62
  5. Distinctive:

    Keep prose terse while ensuring clarity.

    line 69
  6. Distinctive:

    Use lists and sub-lists for long sentences and dense paragraphs.

    line 72

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Coverage

When to use

  • The user wants to address coverage gaps in target code autonomously using the test agent.

Goal

  • Run test subagents sequentially to cover behavioral gaps in target code.

Input

  • Accept optional arguments (file or folder paths).

Workflow

Halt on any Halt conditions entry after every spawn.

  1. Testing Loop:
    • Spawn a test subagent with the optional argument; await its result.
    • Improved: repeat step 1.
    • No Gaps: proceed to step 2.
  2. Report: emit the result per Result directives:
    • Result: Completed when the workflow reaches Report without a halt; Halted when a subagent reports Failed; Failed on any other Halt conditions entry.

Directives

  • Always use the subagent tool for subagent invocation.
  • Pass the argument verbatim to each subagent; never read or expand file-path arguments.
  • Route only from each subagent's Result value.
  • Spawn only the subagents the workflow names.

Constraints

  • Restrict activities to spawning subagents, reading their results, and reporting; never write files, run git operations, activate skills, or prompt the user mid-run.
  • Never run subagents in parallel or concurrently.
  • Halt conditions: halt immediately; report per Report, listing the diagnostic under Findings:
    • A subagent Failed result.
    • A subagent result missing or outside the workflow's literals.
    • A process failure (crash, timeout, AgentError).

Verification

  • Subagents ran one at a time, in workflow order.
  • Every run, halted or not, ended in Report.
  • The orchestrator wrote no file.

Result directives

  • Minimum words. Maximum signal.
  • Return the final execution status block.
  • Keep prose terse while ensuring clarity.
  • Optimize prose for agent, token, and context efficiency.
  • Split actions, findings, and summaries into terse bullet points.
  • Use lists and sub-lists for long sentences and dense paragraphs.
  • Emit the result template as live markdown—never in a code fence.
  • Output nothing outside the template.

Result template

<!-- prettier-ignore-start -->
### Execution Summary

- **Actions**:
  - [Terse list of actions from spawned subagents]
- **Files**:
  - [Terse list of files affected by spawned subagents]
- **Findings**:
  - [Terse list of findings from spawned subagents]
- **Summary**:
  - [Terse list of summary from spawned subagents]

> **Coverage Status** • `[scope]`
> **Result**: [Completed | Halted | Failed]
> **Impact**: [Terse impact statement]
<!-- prettier-ignore-end -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.