Thanks for looking. These are small tools kept deliberately small, so the most useful thing you can send is usually a bug report, not a pull request.
Open an issue. Say what you did, what you expected and what happened instead. Both
tools ship a doctor style check — paste its output and you have saved us the first
three questions.
Open an issue before you write code. Every one of these tools has a scope somebody already argued about, and the answer to "should this exist at all" is written in the README. A five-line issue costs you nothing; a rejected afternoon costs you an afternoon.
- One change per pull request. Say what broke and why this fixes it.
- Run the repository's own checks first. Each one documents its command in its README, and a red pipeline is not reviewed.
- Match the code around you — the naming, the comment density, the idiom.
- Smaller is better. A deletion is the best patch there is.
The tools are MIT. By sending a pull request you agree your work ships under the same licence as the repository you sent it to.
Never in a public issue — see SECURITY.md.