Lean into clig.dev guidelines
Open
- Dominant language
- Jupyter Notebook
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
TODO: Create sub-issues based on https://clig.dev
Thanks @algal for the pointers.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading https://clig.dev and comparing its guidance with nbz's current command-line behavior. The issue asks for sub-issues, so define concrete gaps and acceptance criteria before implementation. No files or tests are named, and the payload does not identify a specific change to verify.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100