lint-doc
Document Linting
Workflow
1. Target Identification
Identify the document to check from recent context (recently edited or discussed files). If no clear target, ask user to provide the file path.
2. Rule Collection
Collect the rules to check against:
- General rules — All document-related rules from
.claude/rules/andCLAUDE.md. Apply rules relevant to the document's language (e.g. text formatting rules for Japanese documents). - Skill-specific rules — If the document was created by a skill (e.g.
analysis-report,technical-writing), read that skill's definition and extract any writing guidelines, constraints, or anti-patterns defined there.
Determine the originating skill from conversation context. If unclear, ask the user.
3. Rule Check
Read the target file and check against all collected rules (both general and skill-specific).
4. Report Findings
List all violations found with:
- Line number
- Violation type
- Current text
- Suggested fix
5. Apply Fixes
Use AskUserQuestion to present the following options:
- Auto-fix all - Apply all suggested fixes
- Review each - Confirm each fix individually
- Report only - Show violations without fixing
Scope Exclusions
Do NOT modify content inside:
- Backticks (inline code, code blocks)
- Database values or API responses
- Quoted text from external sources
More from yusuke-suzuki/dotfiles
resolve-comments
Resolve PR review comments
21fixup
Create a fixup commit and autosquash rebase
19publish
Push commits and create/update pull request
19sync
Sync feature branch with main via rebase
18commit
Create a git commit with Conventional Commits format
18release
Determine next semver tag, push it to trigger production deployment, and publish a GitHub release
6