Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

audit

Sterne0

Forks0

Aktualisiert23. März 2026 um 03:29

Examine evidence (files, logs, code, output) against user instructions and baseline quality factors. Audit only, no fixes.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

benaskins

benaskins/humanpowers

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	audit
description	Examine evidence (files, logs, code, output) against user instructions and baseline quality factors. Audit only, no fixes.

Audit

Examine evidence. Apply the user's instructions. Check the baselines.

Read what the user points you at — files, logs, code, output.
Follow their audit instructions exactly.
Check each finding against the baselines:
- Legibility: can a reader understand this without extra context?
- Ergonomics: does this create friction for the developer?
- Security: does this introduce or miss a vulnerability?
- Reliability: can this fail silently or in a way that's hard to diagnose?
- Consistency: does this follow the patterns established elsewhere in the codebase?
- Completeness: is anything missing, half-implemented, or left as a TODO?
Report findings. Evidence for each — quote the line, show the log, name the file.
No fixes. Audit only. If asked to fix, /iterate.

$ARGUMENTS

Mehr aus diesem Repository

gleiches Repository

ground

benaskins/humanpowers

Orient in project state before starting work

2026-04-210

triage

benaskins/humanpowers

Review open issues and PRs across the workspace to decide what needs action

2026-04-210

iterate

benaskins/humanpowers

Use when executing an implementation plan. Builds in TDD cycles with disciplined commits — one commit per plan step, no unrelated files swept in.

2026-03-230

brainstorm

benaskins/humanpowers

Use before building anything non-trivial — new features, architectural changes, multi-file modifications. Explores intent, requirements, and design before implementation.

2026-03-160

debug

benaskins/humanpowers

Use when diagnosing bugs, test failures, or unexpected behavior. Requires hypotheses before fixes — no jumping to solutions.

2026-03-160

deploy

benaskins/humanpowers

Deploy one or more services end-to-end with health verification

2026-03-160

name	audit
description	Examine evidence (files, logs, code, output) against user instructions and baseline quality factors. Audit only, no fixes.

Audit

Examine evidence. Apply the user's instructions. Check the baselines.

Read what the user points you at — files, logs, code, output.
Follow their audit instructions exactly.
Check each finding against the baselines:
- Legibility: can a reader understand this without extra context?
- Ergonomics: does this create friction for the developer?
- Security: does this introduce or miss a vulnerability?
- Reliability: can this fail silently or in a way that's hard to diagnose?
- Consistency: does this follow the patterns established elsewhere in the codebase?
- Completeness: is anything missing, half-implemented, or left as a TODO?
Report findings. Evidence for each — quote the line, show the log, name the file.
No fixes. Audit only. If asked to fix, /iterate.

$ARGUMENTS