content-reviewer
Review drafts for clarity, structure, evidence quality, and reader usefulness against the project's writing rules. Use when a draft needs a structured review pass before publishing.
- License 许可
- MIT
- 所属仓库
- Eliyce/paqad-ai
- 最近更新
- 2026-11-13
- Stars
- ★ 8
- Forks
- 0
01 前言 Front Matter
- name
- content-reviewer
- description
- Review drafts for clarity, structure, evidence quality, and reader usefulness against the project's writing rules. Use when a draft needs a structured review pass before publishing.
02 资源文件 4
- 资产文件assets/output.template.md329 B
- 参考文档references/review-rubric.md734 B
- 脚本scripts/lint-output.sh716 B
- 脚本scripts/scan-prose.sh1.3 KB
03 SKILL.md 正文
Content Reviewer
What It Does
Runs a structured review pass over a draft so feedback is concrete (line + heuristic + required action) instead of subjective.
Use This When
When a draft is ready for review and the team wants consistent, traceable feedback rather than personal taste.
Inputs
- The draft markdown / copy.
- The project's writing-style file at
docs/instructions/rules/writing-style.mdwhen it exists. references/review-rubric.mdfor the review heuristics.
Procedure
- Run
scripts/scan-prose.sh <draft>to surface candidate issues (filler, hedge, passive, jargon, vague this, long lines, broken links). - For each hit, decide if it's an actual problem given the audience defined by the brief.
- Walk every heuristic in
references/review-rubric.md; never skip a category silently. - Format findings per
assets/output.template.md. - Validate with
scripts/lint-output.sh.
Output Contract
- Match
assets/output.template.md:## Blocking Issuesand## Improvement Opportunities. - Output must pass
scripts/lint-output.sh.
Resources
references/review-rubric.mdscripts/scan-prose.shscripts/lint-output.shassets/output.template.md
04 同仓库更多 Skills
sample-skill
Sample bundled skill fixture
processing-invoices
Turns a supplier invoice into one ledger line. Use when a supplier invoice arrives and needs booking.
processing-invoices
Turns a supplier invoice into one ledger line. Use when a supplier invoice arrives and needs booking.
understand-idea
Chat and Claude Code: Step 1 of the discover journey: clarifies the goal, who benefits, success and constraints into the idea block. Use when the journey directs it to step 1, not directly.
size-work
Chat and Claude Code: Suggest a size for a ticket from comparable finished work, as a labelled suggestion the team still owns. Use it when someone asks "how big is this?", "roughly how much work is ABC-12?", or wants a backlog item sized. It finds the team's sizing scale at first use, picks two to five of the closest finished tickets with links, and gives a size or range with the drivers behind it and a confidence of low, medium or high, lowered and explained when the area's documents are template text. Every result is labelled a suggested size, never a date or a commitment. It writes nothing into the size field unless the user says "set it", and it refuses to overwrite an existing size unless the user asks to replace it. Produces the sizing block of the record.
refine-ticket
Chat and Claude Code: Improve one or more existing tracker tickets without losing the author's intent. Use it when someone wants a ticket read, diagnosed and tidied up ("this ticket is vague", "fix up ABC-12", "split this, it's too big"). It reads each ticket in full and snapshots it with its last-updated time, says what is wrong with evidence, and proposes a field-by-field before and after change set limited to summary, description, labels, parent, links and new child tickets on a split. It writes nothing until an explicit "apply it" bound to that exact change set, re-checks the ticket for conflicting edits just before writing, never replaces rich descriptions with plain text, never deletes or closes a ticket, and reads each ticket back after applying. Produces the existing and changes blocks of the record.