mcpField
Q
quality-review-checklist

quality-review-checklist

github.com/gtmagentsTesting & quality42869 installsUpdated 30w ago
Repository

About quality-review-checklist

A content quality-review skill for documentation teams and contributors. It organizes checks for accuracy, style, accessibility, localization, compliance, and release tracking into reusable review templates.

Key features

  1. 01Accuracy and coverage checks
  2. 02Style and terminology review
  3. 03Accessibility review
  4. 04Localization and compliance checks
  5. 05Version and release tracking
  6. 06QA and sign-off templates

Use cases

  1. 01Review docs before publication
  2. 02Audit inherited content during migrations
  3. 03Train contributors on review steps

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill quality-review-checklist

After installing, type/quality-review-checklistin Claude Code to confirm it loaded.

Details

From the project README

Quality Review Checklist Skill

When to Use

  • Pre-publication QA for docs, tutorials, and release notes.
  • Auditing inherited content during migrations.
  • Training new contributors on required review steps.

Framework

  1. Accuracy & Coverage – verify features, parameters, screenshots, and examples match latest build.
  2. Style & Voice – enforce style guide, terminology, formatting, and tone per audience.
  3. Accessibility – heading hierarchy, alt-text, captions, contrast, keyboard navigation, screen-reader cues.
  4. Localization & Compliance – translation scope, legal disclaimers, export controls, privacy statements.
  5. Version Control – version tags, changelog entries, rollback plan, owner assignments.

Templates

  • QA checklist spreadsheet with pass/fail + notes fields.
  • Reviewer sign-off sheet with timestamps and comments.
  • Issue log for follow-up fixes grouped by severity.

Tips

  • Pair reviewers (technical + editorial) for faster turnarounds.
  • Automate linting scripts (links, markdown, accessibility) and attach results to the checklist.
  • Use with publish-release-documentation for final approvals.

Comments

Markdown supported