Repository documents remain in their original published languages. This guide does not translate external pages.
01Agent install
Install with your agent
Copy the prompt for your agent. It will check the environment and conflicts before following the repository setup and verification instructions.
Help me set up Neat Freak Codex Skill from the public GitHub repository duxinrui9-gif/neat-freak-codex-skill. Read its README, installation instructions, license and source notices first. Check my environment, dependencies and existing same-name installations. Use the Codex Skill installer to install skills/neat-freak only after checking for an existing Skill. Do not overwrite existing files or expose personal data. Stop on conflicts, permission failures or uncertain sources. Run the repository's documented checks and report installation location, version, results and first-use instructions.What it helps with
Neat Freak aligns implementation, README, architecture and handoff at the end of a project stage. It makes completion, verification and remaining risks clear to the next person. It does not replace discovery or safety review.
Prepare
Read the linked repository’s setup guidance, MIT license and source notice. Check your Codex environment and whether a same-name Skill already exists. Stop on conflicts rather than overwriting.
Install
Use the installation prompt above or follow the repository’s built-in Codex installer instructions manually. Install the skills/neat-freak directory, then open a new Codex task so it can be discovered.
First use: a read-only handover
Choose a small, non-production project:
Run a lightweight project handover check.
Read README, AGENTS, architecture and handoff.
Do not delete or rewrite files.
List inconsistencies, unverified work and possible temporary artifacts,
with suggestions ranked by risk.Check that the result respects scope before authorizing document changes.
Understand closure, handover and tidiness
Closure checks deliverables, documents, verification and remaining work. Handover lets someone unfamiliar continue safely. Tidiness separates final deliverables from temporary and private material—it does not mean deleting more.
When to use it
Use it at feature completion, handover, release preparation or a change of project phase. Settle uncertain requirements first.
For a stage handover, check startup instructions, working rules, architecture and current status. For release preparation, check configuration, behavior and public-safety boundaries; report blockers rather than deleting or publishing automatically.
Check the result
- Deliverables match the goal.
- Verification has run, or missing checks are explained.
- Only necessary documentation changed.
- Private configuration and temporary outputs are excluded.
- A new collaborator can find the entry point, boundaries, risks and next step.
The repository provides Skill validation and inventory tests; use its documented commands rather than assuming that a successful copy means a verified install.
Common questions
Will it clean files automatically?
Deletion, overwriting or moving needs explicit scope and authorization. Report first.
What if the project has its own rules?
Read and follow those rules. Neat Freak supplements the handover rather than forcing a new documentation structure.
What if the workspace is already messy?
Separate this task’s edits from existing or uncertain changes. Preserve what cannot be safely attributed.
Source and license
Original Neat Freak: 数字生命卡兹克 (KKKKhazix). Codex adaptation and maintenance: Yuli Du. MIT license. The linked repository holds reusable guidance, not personal project data.