Skip to content
TrustedSkillsbeta
Back to all skills

Pytest Coverage

Official
github·vlatest·testing·MIT

This skill generates pytest coverage reports to assess code test execution and identify gaps for improved reliability.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add github/awesome-copilot --skill pytest-coverage -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

github

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned github/awesome-copilot at 6c4d33b9cf.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
6c4d33b9cf
Manifest
skills/pytest-coverage/SKILL.md
Scanned
0 files
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The pytest-coverage skill integrates with Python's pytest testing framework to measure code coverage during test execution. It provides detailed reports on which parts of the codebase are exercised by tests, helping developers identify untested areas and improve test quality.

When to use it

  • You want to ensure all critical sections of your Python code are tested after writing new features.
  • You're working on a project with multiple contributors and need consistent coverage metrics across different branches or pull requests.
  • Your team is following test-driven development (TDD) practices and needs real-time feedback on test completeness.

Key capabilities

  • Generates code coverage reports in various formats like HTML, XML, and JSON.
  • Integrates seamlessly with pytest for automated testing workflows.
  • Highlights lines of code that are not executed by tests, aiding in debugging and refactoring efforts.

Example prompts

  • "Run pytest with coverage analysis on the test suite."
  • "Generate an HTML coverage report after executing all unit tests."
  • "Show me which functions in utils.py are not covered by tests."

Tips & gotchas

  • Ensure that your project has pytest and coverage.py installed before using this skill.
  • Some code, like conditionals inside functions that aren't triggered during testing, may appear as uncovered even if logically correct. Always review coverage reports in context.