spec-proofreader

Étoiles1

Forks0

Mis à jour30 avril 2026 à 06:43

Reviews spec documents for text quality issues without knowledge of the feature description. Fixes errors directly. Invoked by spec-writer, not directly.

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.

Source

wtsi-hgi

wtsi-hgi/agentskills

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

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Rédacteurs en chefArts, design, divertissement, sports et médias·SOC 27-3041

SKILL.md

readonly

name	spec-proofreader
description	Reviews spec documents for text quality issues without knowledge of the feature description. Fixes errors directly. Invoked by spec-writer, not directly.
context	fork

Spec Proofreader Skill

Read and follow agent-conduct before starting.

You have NO knowledge of the original feature description. Review the spec purely on its own merits as a written document.

Input

Spec path only. Do NOT receive the feature description.

Procedure

1. Read the entire spec.

2. Check for text errors

Repetition: same thing said in different words; redundant acceptance tests.
Contradictions: conflicting statements (e.g. type defined differently in two places).
Undefined terms: types, functions, packages used without definition.
Placeholder text: TODO, TBD, incomplete sections.
Cross-references: all internal references resolve correctly.

3. Check structure and numbering

Sequential section letters (A, B, C...) and story numbers (A1, A2, B1...). No gaps or duplicates.
Every story ID in implementation order exists as an actual story.
Every story appears in the implementation order.
All acceptance tests are inside user story blocks.
All stories are under matching ## Section <Letter>: headings.

4. Check formatting

80-column wrap (code blocks exempt). ASCII only (no em dashes, smart quotes, special chars outside code blocks).
Consistent whitespace, no trailing whitespace, no consecutive blank lines.
Code blocks specify language. Proper heading hierarchy.

5. Fix errors directly. Keep fixes minimal. Check codebase only to resolve

ambiguities.

6. Verdict

PASS - no errors found.
FIXED - list every error and how it was fixed.

Rules

Do NOT check feature coverage (that is spec-reviewer's job).
Do NOT evaluate technical design.
Do NOT add new content.
ONLY fix text errors, formatting, numbering, and consistency.

Plus depuis ce dépôt

même dépôt

bugfix

wtsi-hgi/agentskills

Orchestrates standalone or caller-batched bug fixes via implementor and reviewer subagents using TDD. Handles bugs and verified review findings sequentially, tracks them in a dated checklist, and commits each fix without disrupting a surrounding PR-resolution batch.

2026-07-111

pr-resolver

wtsi-hgi/agentskills

Resolve GitHub PR review comments from humans and Copilot, including reviews already auto-requested or in progress. Use for verified comment resolution, sequential bugfix batching, one-push CI/Copilot cycles, and SHA-aware waits that avoid stale-event loops.

2026-07-111

go-conventions

wtsi-hgi/agentskills

Shared conventions for Go projects. Copyright boilerplate, code quality, GoConvey testing, architecture, and commands. Referenced by go-implementor, go-reviewer, and workflow skills.

2026-07-111

go-implementor

wtsi-hgi/agentskills

Go TDD implementation workflow. References implementation-principles, go-conventions, testing-principles, and agent-conduct.

2026-07-111

go-reviewer

wtsi-hgi/agentskills

Review Go implementations against spec acceptance tests. References implementation-principles, go-conventions, testing-principles, and agent-conduct.

2026-07-111

implementation-principles

wtsi-hgi/agentskills

Shared cross-language delivery workflow and guidance for implementing the simplest sufficient solution, maximizing reuse of existing code, and avoiding speculative abstractions, dependencies, and refactors. Use when implementing or reviewing code in any language.

2026-07-111

name	spec-proofreader
description	Reviews spec documents for text quality issues without knowledge of the feature description. Fixes errors directly. Invoked by spec-writer, not directly.
context	fork

Spec Proofreader Skill

Read and follow agent-conduct before starting.

You have NO knowledge of the original feature description. Review the spec purely on its own merits as a written document.

Input

Spec path only. Do NOT receive the feature description.

Procedure

1. Read the entire spec.

2. Check for text errors

Repetition: same thing said in different words; redundant acceptance tests.
Contradictions: conflicting statements (e.g. type defined differently in two places).
Undefined terms: types, functions, packages used without definition.
Placeholder text: TODO, TBD, incomplete sections.
Cross-references: all internal references resolve correctly.

3. Check structure and numbering

Sequential section letters (A, B, C...) and story numbers (A1, A2, B1...). No gaps or duplicates.
Every story ID in implementation order exists as an actual story.
Every story appears in the implementation order.
All acceptance tests are inside user story blocks.
All stories are under matching ## Section <Letter>: headings.

4. Check formatting

80-column wrap (code blocks exempt). ASCII only (no em dashes, smart quotes, special chars outside code blocks).
Consistent whitespace, no trailing whitespace, no consecutive blank lines.
Code blocks specify language. Proper heading hierarchy.

5. Fix errors directly. Keep fixes minimal. Check codebase only to resolve

ambiguities.

6. Verdict

PASS - no errors found.
FIXED - list every error and how it was fixed.

Rules

Do NOT check feature coverage (that is spec-reviewer's job).
Do NOT evaluate technical design.
Do NOT add new content.
ONLY fix text errors, formatting, numbering, and consistency.