qa-check
Run QA Checks Before Pull Requests
Teams need fast PR checks before code review. This skill runs a clear QA workflow for backend and frontend validation.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "qa-check" from https://skillstore.io/skills/crearize-qa-check.md and its manifest at https://skillstore.io/api/skills/crearize-qa-check/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "qa-check". Run a full QA check before opening a pull request.
Expected outcome:
Overall result: failed. Backend checks passed. Frontend build failed on type errors. Next steps: fix type errors, rerun build, then rerun full QA.
Using "qa-check". Run a frontend-only check with coverage enabled.
Expected outcome:
Overall result: warning. Lint and build passed. Coverage is below the target. Next steps: add tests for low-coverage UI logic.
Using "qa-check". Run a backend check without coverage.
Expected outcome:
Overall result: passed with coverage skipped. Gradle checks passed. Next steps: run coverage before final review if the team requires it.
Security Audit
SafeThe skill is a project-specific QA checklist that documents Gradle and pnpm validation commands. All static findings were false positives from Markdown backticks, benign /dev/null redirection, or a heuristic entropy signal; no prompt injection, exfiltration, or destructive workflow was found.
Risk Factors
⚙️ External commands (40)
📁 Filesystem access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/crearize-qa-check/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/crearize-qa-check?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/crearize-qa-check?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/crearize-qa-check/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/crearize-qa-check.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Crearize. (2026). qa-check security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/crearize-qa-check/audits/10BibTeX citation
@techreport{crearize-crearize-qa-check-2026,
author = {Crearize},
title = {qa-check security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/crearize-qa-check/audits/10},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "qa-check security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "Crearize"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/crearize-qa-check/audits/10"
identifiers:
- type: other
value: "skillstore:crearize-qa-check:audit:10"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Backend readiness check
Validate Gradle checks and coverage before asking for backend code review.
Frontend PR validation
Run lint, build, and coverage checks for frontend changes before opening a PR.
Release quality gate
Review combined backend and frontend status before approving release branches.
Try These Prompts
/qa-check
/qa-check target="frontend"
/qa-check target="backend" skip_coverage_check=true
Run qa-check for both targets, include coverage, and list each failing command with the recommended fix order.
Best Practices
- Run the skill from the intended project root.
- Keep coverage enabled for final PR readiness checks.
- Review failed command logs before applying fixes.
Avoid
- Do not treat skipped coverage as final approval.
- Do not run the workflow in unrelated repository layouts.
- Do not ignore failed lint, test, or build steps.