skills/rewrite-rustdoc/SKILL.md
Rewrite Rust documentation comments to ensure all documentation and comments are in English, following rustdoc guidelines. Use when the user wants to clean up Rust documentation, translate Chinese comments to English, fix missing documentation, or ensure rustdoc compliance in a Rust codebase.
npx skillsauth add jim60105/copilot-prompt rewrite-rustdocInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Ensure all Rust documentation and comments are exclusively written in English, following rustdoc guidelines.
Determine which files to process:
src/ directory.Conduct a comprehensive review to ensure all documentation and comments are in English.
Search for Chinese characters in the source code:
rg -n "[\u4e00-\u9fff]" src/
Check for missing documentation:
cd src/ && cargo clippy -- -W missing_docs
Replace src/ with the user-specified location if provided.
Refer to ./docs/rustdoc-guidelines.md for documentation structure and style standards.
Ensure all corrections adhere strictly to the documentation guidelines.
Repeat the search and revision process iteratively until no further occurrences require modification.
development
Generate images via the Stable Diffusion WebUI / Forge HTTP API (AUTOMATIC1111-compatible `/sdapi/v1/*`). Use when the user wants to (1) discover or pick a model / extra module (TE/VAE) / sampler / scheduler / style preset from a running sd-webui server, (2) generate an image with a given prompt (txt2img), (3) check generation progress, (4) cancel/interrupt an in-flight generation, (5) inspect or change a global sd-webui option (e.g. active checkpoint), or (6) test connectivity. This skill talks to a *generic* sd-webui-compatible server (AUTOMATIC1111, Forge, reForge, sd-webui-forge-classic). Do NOT trigger for requests that are purely writing the prompt itself.
testing
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
development
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
data-ai
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.