Skill Prose Contract Review
Use this Skill when its method fits the current quality task.
StatusStable
TypeAtomic Skill
DomainSoftware testing
SDLCTest design
Good forQA / DEV
LanguageChinese / English
EvalsEvals ✓
Synced2026-09-15
Why this Skill
It turns this Skill's method into a quality input that can be executed, reviewed, and reused.
When to use
Use this Skill
- Use this Skill when its method fits the current quality task.
Common pitfalls
- No content is available for this Skill yet.
Input
Minimum Input
- Confirm scope and document role.
Recommended Input
- Project goal
- Test scope
- Constraints
Optional Context
- Relevant code or configuration
- Historical results
- Logs and metrics
Output
The output follows this Skill's method and makes facts, assumptions, risks, and next steps explicit.
These are the Skill's expected output requirements, not evidence that it ran in a real project.
- 01Confirm scope and document role.
- 02Trace trigger → input → rules → output → constraints → verification.
- 03Report blockers, important suggestions, location, impact, and evidence.
- 04List missing information and unverified claims.
How It Works
- 01Confirm scope and document role.
- 02Trace trigger → input → rules → output → constraints → verification.
- 03Report blockers, important suggestions, location, impact, and evidence.
- 04List missing information and unverified claims.
Install & Quick Start
Install command / SHELL
npx skills add \
https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/skill-engineering/skill-prose-review
-gskill-prose-review.prompt
@skill skill-prose-review
Using the current project context, produce an actionable result following this Skill.
Additional context:
[Paste project context or requirement]---
name: skill-prose-review
description: Use this skill when reviewing the contract completeness of Skills, Prompts, metadata, or QA documentation; triggers include Skill prose review, Prompt review, and contract audit.
---
# Skill Prose Contract Review
## When to use
- Review a Skill, Prompt, metadata, example, or output format.
- Check whether prose is executable, independently installable, and verifiable.
## Workflow
1. Confirm scope and document role.
2. Trace trigger → input → rules → output → constraints → verification.
3. Report blockers, important suggestions, location, impact, and evidence.
4. List missing information and unverified claims.
## Constraints
- Do not invent behavior, tools, or facts.
- Do not report static reading as runtime validation.
- Do not rewrite files unless explicitly requested.
## On-demand loading
- Read `prompts/skill-prose-review.md` before producing the review.
- Use `evals/` for evaluation and report static and runtime evidence separately.
## Final checklist
- [ ] Scope and document role are explicit
- [ ] Input, output, constraints, and verification are covered
- [ ] Gaps and evidence levels are stated
- [ ] No unauthorized file changes