Add `charmcraft lint` to enforce Canonical recommendations
Metadata
Current evaluation
Proposes adding a charmcraft lint command to enforce consistent naming conventions for charm actions and options, currently acknowledged by maintainers but blocked pending the resolution of issue 2315.
Suggested action: keep open
Reason: The issue has been explicitly acknowledged by a maintainer who confirmed it is on the roadmap and deferred pending the resolution of a related tracking issue (#2315). It remains relevant and valid, so it should be kept open despite the period of inactivity.
Staleness:
65
Complexity:
55
Confidence:
85
Support Request:
10
Issue body
### What needs to get done
Hi,
TL;DR: charm must follow same approach in naming actions/options/...: use `-` or `_` (c) Jon/codestyle.
When developers adding the same feature to the different charms, they are following muscle memory and often missing this point.
It cause issues like: https://warthogs.atlassian.net/browse/DPE-7741 (which is expensive and annoying to fix).
Proposal add `charmcraft lint` to help charmers control it on CI/CD.
E.g. it can check consistency of `_`/`-` and error blocking divergence.
We can also warn this on `charmcraft pack`, but without error nobody notice it on CI.
Tnx!
### Why it needs to get done
To settle the high standards in charms quality avoiding divergences.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| 2026-06-15 14:08:40.834942+00:00 | qwen3.6-35b-a3b-mtp-q6 |
Staleness:
65
Complexity:
55
Confidence:
85
Support Request:
10
|
keep open | Proposes adding a charmcraft lint command to enforce consistent naming conventions for charm actions and options, currently acknowledged by maintainers but blocked pending the resolution of issue 2315. |
| 2026-06-15 14:05:46.772737+00:00 | pending | — | — | — |