Andrew Gleave 的 Agent 技能
改善推理、代码可读性、工程决策与界面文字。
这套五技能包组合了批判理性主义、代码整理、五步工程流程、界面文案和 Git 历史诊断，根目录下的技能文件夹构成作者完整公开合集。
适用场景
- 质疑需求并简化工程工作
- 诊断代码库历史与可读性
- 审阅界面措辞和推理过程
使用方法
提供相关需求、界面文字或仓库。使用 navvy 时保留 Git 历史，使诊断能够先从变更规律开始。
Skills
5-steps
Challenges requirements, removes unnecessary work, and simplifies design before writing code. Activates when asked to build, implement, automate, add a feature, create a service, migrate, or replace a process. Does not activate for general code writing, bug fixes, or simple edits.
andrewgleave/skillscleanse
Review code for readability, then simplify it to be easy to follow and understand. Use this skill when the user wants to simplify code, improve readability, clean up for handoff, make code skimmable, reduce complexity, refactor for clarity, strip boilerplate, prepare code for future maintainers, or make a codebase easier to pick up. Trigger liberally — any request touching readability, simplification, cleanup, or "make this easier to understand" should use this skill. Also trigger when the user says things like "review this", "clean this up", "tidy this", "make this simpler", "reduce complexity", "flatten this", "strip the noise", or "I want to understand this code quickly next time I open it".
andrewgleave/skillscritical-reasoning
Apply critical rationalist epistemology (Popper, Deutsch) to evaluate reasoning, identify errors, and refine understanding. Use when the user explicitly requests help with reasoning - phrases like "help me think this through", "does this make sense", "any flaws in this", "what am I missing", "critique this", "is this reasoning sound", "stress test this idea", "devil's advocate", or any request to evaluate arguments, identify logical problems, or improve thinking. Also use when errors in reasoning are significant enough to materially affect the user's goals, even if not explicitly requested.
andrewgleave/skillsnavvy
Diagnose a codebase through its git history before reading any code. Surfaces churn hotspots, bus factor risks, bug clusters, velocity trends, and firefighting patterns. Only invoked directly via /navvy — does not auto-trigger.
andrewgleave/skillswriting-for-interfaces
Use when someone asks to write, rewrite, review, or improve text that appears inside a product or interface. Examples: "review the UX copy", "is there a better way to phrase this", "rewrite this error message", "write copy for this screen/flow/page", reviewing button labels, improving CLI output messages, writing onboarding copy, settings descriptions, or confirmation dialogs. Trigger whenever the request involves wording shown to end users inside software — apps, web, CLI, email notifications, modals, tooltips, empty states, or alerts. Also trigger for vague requests like "review the UX" where interface copy review is implied. Do NOT trigger for content marketing, blog posts, app store listings, API docs, brand guides, cover letters, or interview questions — this is a technical writing skill for interface language.
andrewgleave/skills