qa-report

Generates an HTML quality report combining pytest results, coverage, and secret scanning.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill qa-report-karentenorio963
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-report
Source: https://github.com/KarenTenorio963/curso-mcp-karentenorio/tree/main/entregas/s4/mi-proyecto-speckit/.agents/skills/qa-report
Command: npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill qa-report-karentenorio963

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pytest, pytest-json-report, pytest-cov.

What problem does it solve? Manually checking test results, code coverage, and exposed secrets before shipping code is slow and error-prone. This Skill automates the entire quality gate and produces a single HTML verdict. ## Core Features & Use Cases - Automated Test & Coverage Run: Executes pytest with JSON reporting and coverage measurement against a configurable threshold (50% minimum). - Secret Detection: Scans Python source files for hardcoded API keys, passwords, and tokens using regex patterns. - Git Hygiene Verification: Uses git itself (not just .gitignore text) to verify .env is ignored and not tracked in history, plus checks for .env.example. - Use Case: Before merging a feature branch, run this Skill to get a single APROBADO or REQUIERE CORRECCIÓN verdict in reporte-qa.html, with the top issues listed if it fails. ## Quick Start Run the QA report skill and tell me the final verdict with a one-line summary of my project's quality status.

Frequently Asked Questions about qa-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a QA report for a Python project?▼

Run the generar_reporte.py script with uv, which executes pytest with JSON reporting and coverage, scans for secrets, and writes a reporte-qa.html file with a final APROBADO or REQUIERE CORRECCIÓN verdict.

How to detect hardcoded secrets in Python source code?▼

The script scans all .py files under src/ using regex patterns matching api_key, secret, password, and token assignments with string values of six or more characters, listing each finding in the HTML report.

What coverage threshold does the QA report require?▼

The report requires at least 50% code coverage to pass, measured by pytest-cov against the src directory. Projects below this threshold receive a REQUIERE CORRECCIÓN verdict even if all tests pass.

Why does the script use git commands instead of reading .gitignore?▼

A .gitignore file can claim anything without git actually respecting it. The script uses git ls-files and git check-ignore as the source of truth to confirm .env is genuinely ignored and not already tracked in history.

What happens if .env is already tracked by git?▼

The report flags it as critical because the secret may already exist in git history. Fixing .gitignore alone is insufficient; the file must be removed from the repository history to pass the hygiene check.