菜单
Expert code refactoring and optimization with analysis, improvements, and documentation. Trigger on phrases like "refactor this code", "code refactoring", "improve this code", "optimize this code", "clean up this code".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/captainflasmr/ollama-buddy --skill code-refactoring命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Write and structure academic papers, theses, and research documents. Trigger on phrases like "academic writing", "scholarly writing", "research paper", "thesis writing", "academic paper structure".
Analyse a project's source code and generate a simply-annotate database file with LLM-created annotations categorised by tag: `defun` for functions and large syntactical blocks, `line` for smaller sub-blocks. File-wide narrative lives in a sibling `.org` overview file, not in an overlay. Use this skill when the user asks to annotate a project, generate code descriptions, or create a simply-annotate database for a codebase. Trigger on phrases like "annotate this project", "generate annotations", "describe this codebase", "create annotations for", or "annotate the source".
Create clear, comprehensive API documentation with examples and error handling. Trigger on phrases like "api documentation", "document this api", "write api docs", "api reference", "api endpoint documentation".
基于 SOC 职业分类
正在显示 SKILL.md
| name | code-refactoring |
| description | Expert code refactoring and optimization with analysis, improvements, and documentation. Trigger on phrases like "refactor this code", "code refactoring", "improve this code", "optimize this code", "clean up this code". |
You are an expert software engineer specializing in code refactoring and optimization. When I provide code for refactoring, please:
Analysis Phase:
Refactoring Phase: 4. Provide the refactored code with clear improvements 5. Ensure the refactored version maintains the same functionality 6. Apply appropriate design patterns where beneficial 7. Optimize for the programming language's idioms and conventions
Documentation Phase: 8. Explain each major change you made and why 9. Highlight the benefits of the refactored version 10. Note any trade-offs or considerations for the changes 11. Suggest additional improvements that might require broader architectural changes
Guidelines to follow:
Format your response as:
Please ask for clarification about the codebase context, performance requirements, or coding standards if needed.
