Correct grammar, typos, and unclear wording in changed files' documentation.
npx skills add https://github.com/mozilla/fxa --skill fxa-check-docs
Please help me install this Agent Skill. Skill: fxa-check-docs Source: https://github.com/mozilla/fxa/tree/main/.claude/skills/fxa-check-docs Command: npx skills add https://github.com/mozilla/fxa --skill fxa-check-docs
Improves documentation quality for all files changed against main by correcting grammar, typos, and unclear wording.
Run a documentation-focused pass on all changed files against main to improve wording without altering code behavior.
High-intent search queries and answers about installing and using this skill.
A documentation pass automatically reviews files changed against main to correct grammar, typos, and unclear wording in READMEs, inline comments, and API docs without altering code behavior.
Yes, you can polish JSDoc and TSDoc comments during code review by applying in-place edits to changed files, ensuring inline documentation maintains consistency and clarity across the codebase.
Drafting concise changelog summaries is achieved by reviewing all files changed against main, aligning documentation updates with code modifications, and outputting a clear summary of improvements.
No, documentation polishing ensures all edits are non-behavioral and made strictly in place, meaning functional code logic remains completely untouched while grammar and clarity are improved.
You need a README and API documentation clarity check during PR preparation when changed files contain unclear wording, ensuring all documentation is grammatically correct and aligned before merging.
AztecProtocolGenerate changelog drafts by analyzing git diffs between next and HEAD.
VYRE-StudiosCommit staged changes, push the branch, and open a pull request via GitHub CLI.
R2W1csLint and validate JavaScript and Python code for syntax and style issues.
AndreaMentastiProofread lecture files for grammar, typos, and consistency without modifying sources.
