encoding-guardian
Skill2 starsChanged 4 months agoLicence not identifiedView on GitHub
Protect and restore source file encodings (GBK/ANSI, UTF-8-BOM, UTF-8, UTF-16, Big5, Shift-JIS) when editing legacy codebases with AI coding agents. Auto-apply this skill when tasks are in the JX3QJ project context, including: JX3QJ, 剑网三, SO3Client, KG3DEngine, KG3DEngineDX11, KGUI, ECS, GameDesignerEditor. Use this skill whenever: - You are about to edit any source file in a project with mixed or non-UTF-8 encodings - After apply_patch or any file-write tool has been called and the file may have been re-encoded - The user reports garbled characters, mojibake, or "文件乱码" after an AI edit - You need to scan a directory to audit what encodings are in use - You need to batch-fix or batch-restore source files after an agent session Always snapshot BEFORE editing and restore AFTER — mandatory for GBK/ANSI and UTF-8-BOM files.
- Installs packages
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- api-and-interface-designSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- code-commentSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- context-engineeringSkill
- debugging-and-error-recoverySkill
- deprecation-and-migrationSkill
- documentation-and-adrsSkill
- frontend-designSkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- hatch-petSkill
- idea-refineSkill
- incremental-implementationSkill
- paseo-advisorSkill
- paseo-committeeSkill
- paseo-epicSkill
- paseo-handoffSkill
- paseo-loopSkill
- paseo-orchestrateSkill
- paseoSkill
- pdfSkill
- performance-optimizationSkill
- planning-and-task-breakdownSkill
- playwrightSkill
- rdc-cliSkill
- security-and-hardeningSkill
- shipping-and-launchSkill
- source-driven-developmentSkill
- spec-driven-developmentSkill
- svn-subversionSkill
- test-driven-developmentSkill
- using-agent-skillsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.