メニュー
Guides holistic skill updates through refactoring rather than patching, maintaining quality and conciseness. Use when adding features to existing skills, fixing skill issues, restructuring for clarity, or incorporating user feedback.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | updating-skills |
| description | Guides holistic skill updates through refactoring rather than patching, maintaining quality and conciseness. Use when adding features to existing skills, fixing skill issues, restructuring for clarity, or incorporating user feedback. |
Refactor, don't patch. When updating a skill, review and restructure the entire skill to maintain quality and coherence.
Follow this process for every skill update:
Update Checklist:
- [ ] Step 1: Assess current state (document issues)
- [ ] Step 2: Gather new requirements
- [ ] Step 3: Plan new information architecture
- [ ] Step 4: Refactor skill holistically
- [ ] Step 5: Validate conciseness (<200 lines main)
- [ ] Step 6: Test updated skill
- [ ] Step 7: Document changes made
Before making changes, evaluate:
Symptom: SKILL.md > 300 lines
Solution:
Wrong approach: Append new section Right approach:
Process:
After updates, verify:
For detailed strategies:
Before committing updates, ask:
Provides deep architectural insights into Topcat's implementation including module structure, DAG algorithms, layer system, analysis capabilities, and schema operations. Use when exploring Topcat internals, understanding algorithms, extending functionality, or debugging complex issues.
Guides graph export and visualization in multiple formats. Use when visualizing dependencies, generating documentation, integrating with analysis tools, or creating diagrams for reports.
Guides schema-based organization and analysis for multi-schema database projects. Use when working with multiple schemas, analyzing cross-schema dependencies, or filtering operations by schema.
Guides dependency analysis and safe cleanup operations in Topcat. Use when analyzing dead branches, finding orphans, detecting cycles, cleaning unused files, or integrating with CI/CD pipelines.
Guides testing and debugging of Topcat including running tests, writing new test cases, and debugging issues. Use when working with Topcat's test suite, testing analysis commands, debugging dependency problems, analyzing performance, or setting up continuous integration.
Systematically runs clippy and fixes linting issues following project patterns. Use when running lints, addressing clippy warnings, or improving code quality before commits.