lean-golf
Use when simplifying a working Lean proof while preserving its full statement and definition context.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- lean-golf
- description
- Use when simplifying a working Lean proof while preserving its full statement and definition context.
03 SKILL.md 正文
Simplify a proof without changing its claim
Input: verified declaration and scope. Output: a clearer checked proof or a reason to keep the existing one.
Save the owned baseline and read the full elaborated signature, surrounding
variables, local instances, attributes and definitions. Use lean-search for
direct reusable facts. Try one meaningful simplification at a time: replace
redundant intermediates, use a suitable library lemma, or simplify tactic flow.
Compile each candidate, compare the complete signature/context, and inspect
axioms using lean-verify. A shorter proof that weakens hypotheses or changes
a definition is not an acceptable golf. Keep useful proof comments. A stable
terminal tactic may be clearer than a long mechanically squeezed replacement.
Retain manuscript-facing wrappers that have a correspondence consumer.
If performance worsens, measure with lean-profile. Helper extraction goes
through lean-decompose/lean-refactor; generality changes use lean-generalize
as a separate operation. Discard only this attempt's failing changes, never
other contributors' edits. Return before/after evidence and any remaining issue.
Example: replace an unnecessary chain of equalities with a checked library application while keeping every binder and the source-facing declaration name.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code