spelling-grammar-checker

Correct spelling and grammar errors in user-facing text with severity reports.

2|2|Updated Apr 7, 2013
One-click install
npx skills add https://github.com/warpcode/dotfiles --skill spelling-grammar-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spelling-grammar-checker
Source: https://github.com/warpcode/dotfiles/tree/main/generic/.config/opencode/skills/spelling-grammar-checker
Command: npx skills add https://github.com/warpcode/dotfiles --skill spelling-grammar-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyzes documentation, UI strings, and user-facing text for spelling, grammar, clarity, and style.

Core Features & Use Cases

  • Automated recommendations for spelling and grammar improvements.
  • Prioritized validation with HIGH/MEDIUM/LOW severities.
  • Suggest external tooling invocations (codespell, languagetool, etc.).

Quick Start

Review docs/README.md for spelling and grammar issues.

Frequently Asked Questions about spelling-grammar-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check documentation for spelling and grammar errors?

Spelling and grammar checking analyzes your documentation, UI strings, and user-facing text to identify errors with severity levels (HIGH, MEDIUM, LOW). It extracts natural-language content, ignores code blocks unless requested, and produces a structured report showing location, original text, corrected text, and rationale for each issue.

Can I get patch suggestions for grammar corrections?

Yes. When automatic fixes are requested, the Skill returns optional patch suggestions (diffs) for corrections without applying changes directly. You receive structured recommendations that include corrected text and rationale, letting you review and decide which fixes to implement.

What types of content can be analyzed for style and clarity issues?

The Skill analyzes documentation, UI strings, comments, and other public-facing content. It classifies findings by severity and can suggest external tooling invocations like codespell and languagetool for deeper validation across your project.

How are spelling errors prioritized in the report?

Findings are classified with HIGH, MEDIUM, or LOW severity ratings. The structured report includes line numbers and locations, so you can prioritize critical issues first and address less urgent style improvements later.

Does this work with code files and inline comments?

Yes. The Skill extracts natural-language text from documentation and UI strings while ignoring code blocks by default. You can request analysis of comments and inline text if needed, with results returned as structured findings without automatic changes.