humanize-beagle
Rewrite AI-generated developer text to sound human — fix inflated language, filler, tautological docs, and robotic tone. Use after review-ai-writing identifies issues.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/anderskev/humanize-beagleHumanize
Apply fixes from a previous review-ai-writing run with automatic safe/risky classification.
Usage
/beagle-docs:humanize-beagle [--dry-run] [--all] [--category <name>]
Flags:
--dry-run- Show what would be fixed without changing files--all- Fix entire codebase (runs review with --all first)--category <name>- Only fix specific category:content|vocabulary|formatting|communication|filler|code_docs
Instructions
Hard gates
Advance past destructive or evidence-bound steps only when each PASS is true (commands and artifacts—not “I checked mentally”):
- G1 — Safe to edit files — PASS:
git status --porcelainis empty, orgit stash push -u -m "beagle-docs: pre-humanize backup"exits 0. - G2 — Review input is real JSON with expected shape — PASS:
.beagle/ai-writing-review.jsonexists and the file parses as JSON with agit_headkey and afindingsvalue that is an array (possibly empty). Use thejq -ecommand in step 3, or the same checks withjson.loadin Python. If this fails, stop with a parse/validation error—do not apply fixes. - G3 — References before rewrites — PASS: For each finding you will edit, the
references/*.mdfiles required by step 4 for that category/type are read in this session before you change text. - G4 — Per-file validation — PASS: Every modified file passes the step 8 check for its type; otherwise run
git checkout -- "$file"for that file and do not list it as OK in the summary. - G5 — Delete review file only on full success — PASS: Run
rm .beagle/ai-writing-review.jsononly when G4 holds for all files you are keeping unchanged from validation failures (aligns with step 10).
1. Parse Arguments
Extract flags from $ARGUMENTS:
--dry-run- Preview mode only--all- Full codebase scan--category <name>- Filter to specific category
2. Pre-flight Safety Checks
# Check for uncommitted changes
git status --porcelain
If working directory is dirty, warn:
Warning: You have uncommitted changes. Creating a git stash before proceeding.
Run `git stash pop` to restore if needed.
Create stash if dirty:
git stash push -u -m "beagle-docs: pre-humanize backup"
G1 PASS: Either the working tree was already clean, or the stash command exited 0.
3. Load Review Results
Check for existing review file:
cat .beagle/ai-writing-review.json 2>/dev/null
If file missing:
- If
--allflag: Run/beagle-docs:review-ai-writing --allfirst - Otherwise: Fail with: "No review results found. Run
/beagle-docs:review-ai-writingfirst."
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-anderskev-humanize-beagle": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
explanation-docs
Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do
tutorial-docs
Tutorial patterns for documentation - learning-oriented guides that teach through guided doing
pytest-code-review
Reviews pytest test code for async patterns, fixtures, parametrize, and mocking. Use when reviewing test_*.py files, checking async test functions, fixture usage, or mock patterns.
reference-docs
Reference documentation patterns for API and symbol documentation. Use when writing reference docs, API docs, parameter tables, or technical specifications. Triggers on reference docs, API reference, function reference, parameters table, symbol documentation.
serde-code-review
Reviews serde serialization code for derive patterns, enum representations, custom implementations, and common serialization bugs. Use when reviewing Rust code that uses serde, serde_json, toml, or any serde-based serialization format. Covers attribute macros, field renaming, and format-specific pitfalls.