Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

quality-checks

Étoiles11

Forks1

Mis à jour22 mai 2026 à 15:01

Use when asked to "fix things", "qa", "run tests and fix things", "test until clean", or similar requests to iteratively run quality checks and fix failures until everything passes. Don't use for single-purpose tasks like running only tests or only linting without fixes.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

tedivm

tedivm/opencode-config

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	quality-checks
description	Use when asked to "fix things", "qa", "run tests and fix things", "test until clean", or similar requests to iteratively run quality checks and fix failures until everything passes. Don't use for single-purpose tasks like running only tests or only linting without fixes.
license	MIT
metadata	{"author":"Robert Hafner","source":"https://github.com/tedivm/opencode-config"}

Quick start

Discover project tooling, run all quality checks, fix failures, and repeat until everything passes.

Workflow

Check for task definitions in AGENTS.md, Makefile, justfile, or package.json scripts
Identify commands for: tests, linting, formatting, documentation builds, and other chores
Run all checks and capture results
If any check fails, fix the issues
Re-run formatting/chores, then the full test suite
Repeat steps 4-5 until all checks pass
Report final status

Constraints

Prefer project-defined tooling (AGENTS.md, Makefile, justfile, package.json) over guessing
On subsequent runs, reuse previously discovered commands instead of re-researching
Always re-run the full suite after each fix — do not assume partial re-checks are sufficient
Report all failures with file paths and line numbers before fixing

Checklist

Test suite executed
Lint/format checks completed
Documentation/chores run (if applicable)
All failures fixed
Final pass confirms everything green

Plus depuis ce dépôt

même dépôt

converting-to-markdown

tedivm/opencode-config

Use when converting files to Markdown format for LLM consumption, document analysis, or text extraction. Supports PDF, Office documents, images, audio, HTML, and more via Microsoft's markitdown. Don't use for simple text file reads, existing Markdown files, or when the file is in a usable format.

2026-07-0611

create-command

tedivm/opencode-config

Use when creating or modifying custom opencode commands in the `commands/` directory. Covers markdown command files, frontmatter options (description, agent, model, subtask), prompt templates with $ARGUMENTS, shell output injection, and file references.

2026-07-0611

rendering-mermaid

tedivm/opencode-config

Use when rendering mermaid diagrams to PNG, SVG, or PDF images. Handles both .mmd files and inline mermaid code blocks in markdown files. Don't use for creating mermaid syntax or GraphViz/DOT diagrams.

2026-07-0611

document-architecture

tedivm/opencode-config

Use when creating a comprehensive architecture document for a codebase. First explores the codebase using the exploring-code skill, then writes a detailed architecture document. Don't use for quick documentation lookups or single-file questions: only use when asked to create or update architectural documents.

2026-06-2211

exploring-code

tedivm/opencode-config

Use to do a thorough exploration of an existing codebase. Always use this when asked to explore a codebase/repo/project. Always use it when starting a task that requires deep knowledge of the codebase. Don't use for quick lookups or single-file questions.

2026-06-2211

github-actions

tedivm/opencode-config

You MUST use when creating, modifying, or reviewing GitHub Actions workflow files. For security reasons it is VITAL that you use this skill when working with third party actions (including `actions/checkout` and other official actions).

2026-06-2211

name	quality-checks
description	Use when asked to "fix things", "qa", "run tests and fix things", "test until clean", or similar requests to iteratively run quality checks and fix failures until everything passes. Don't use for single-purpose tasks like running only tests or only linting without fixes.
license	MIT
metadata	{"author":"Robert Hafner","source":"https://github.com/tedivm/opencode-config"}

Quick start

Discover project tooling, run all quality checks, fix failures, and repeat until everything passes.

Workflow

Check for task definitions in AGENTS.md, Makefile, justfile, or package.json scripts
Identify commands for: tests, linting, formatting, documentation builds, and other chores
Run all checks and capture results
If any check fails, fix the issues
Re-run formatting/chores, then the full test suite
Repeat steps 4-5 until all checks pass
Report final status

Constraints

Prefer project-defined tooling (AGENTS.md, Makefile, justfile, package.json) over guessing
On subsequent runs, reuse previously discovered commands instead of re-researching
Always re-run the full suite after each fix — do not assume partial re-checks are sufficient
Report all failures with file paths and line numbers before fixing

Checklist

Test suite executed
Lint/format checks completed
Documentation/chores run (if applicable)
All failures fixed
Final pass confirms everything green