leanprover / leanprover/reference-manual
Describe `lean4checker`
Open
Nobody has claimed this yet.
doc-request
- Dominant language
- Lean
- Stars
- 129
- Forks
- 67
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
What question should the reference manual answer?
What is lean4checker, what problem does it solve, and how to use it?
Additional context
This came up in a Zulip thread.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the reference manual's existing structure and the linked Zulip discussion for context on lean4checker. Add a section explaining what it is, the problem it solves, and how to use it; done means these questions are answered clearly in the manual.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100