القائمة
Find and remove legacy Ito-managed files left behind by older Ito versions. Use when a repo may contain stale or renamed Ito skills, commands, prompts, adapters, or planning artifacts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Implement Ito Lite markdown changes by reading proposal/spec/design/tasks artifacts and updating manual task statuses. Use when applying or executing a prompt-only Ito Lite change without the ito CLI.
Archive completed Ito Lite changes by manually merging spec deltas into current specs and moving the change to archive. Use after implementation and verification when no ito CLI is available.
Create prompt-driven Ito Lite change proposal packages in markdown. Use for drafting proposal.md, spec deltas, optional design.md, and tasks.md without the ito CLI or validation executable.
Review Ito Lite markdown proposal packages before implementation. Use to check proposal.md, spec deltas, design.md, and tasks.md for consistency, risk, testability, and manual validation without the ito CLI.
Initialize a markdown-only Ito Lite workspace with no executables. Use when setting up prompt-driven change proposals, creating .ito-lite/project.md, or preparing a repo for Ito-style specs, changes, and tasks without the ito CLI.
Coordinate the prompt-only Ito Lite workflow for proposals, specs, tasks, reviews, implementation, and archive without the ito executable. Use when the user asks for Ito-style planning, change proposals, lightweight specs, or markdown-only change management.
| name | ito-cleanup |
| description | Find and remove legacy Ito-managed files left behind by older Ito versions. Use when a repo may contain stale or renamed Ito skills, commands, prompts, adapters, or planning artifacts. |
Use this skill to audit a repository for legacy Ito-managed files and remove only the files the user approves.
Run the cleanup instruction generator:
ito agent instruction cleanup
Follow the returned instruction step by step.
Report every deletion candidate before removing anything. Include:
Ask the user to confirm the exact deletion list.
Delete only confirmed paths, then rerun the scan and show git status --short.