Use Craft Application's Linter Service
Metadata
Current evaluation
Migrate linting commands to the shared Craft Application Linter Service to unify UX and eliminate code duplication across craft apps; currently triaged and awaiting assignment after 144 days of inactivity.
Suggested action: keep open
Reason: The issue is already triaged and clearly scoped as a valid architectural refactor. Despite ~5 months of inactivity, there is no evidence it has become irrelevant or outdated, and it was initiated by a maintainer. It should remain open for future implementation.
Staleness:
50
Complexity:
65
Confidence:
85
Support Request:
0
Issue body
### Check existing issues
- [x] I've verified that this request isn't described by any existing issues.
### Request
Migrate to the Linter Service as implemented at https://github.com/canonical/craft-application/issues/782
* All linters are implementations of the Craft Application class
* The lint command uses the LinterService
* Any other uses of linters use the LinterService
### The problem it solves
Snapcraft and Charmcraft lint snaps and charms respectively at the end of the lifecycle.
These linters don’t share common code and don’t have a similar UX. Additionally, there isn’t a way to add linters to other *craft apps without significant code duplication.
Supersedes #2315
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| 2026-06-15 12:49:18.098544+00:00 | qwen3.6-35b-a3b-mtp-q6 |
Staleness:
50
Complexity:
65
Confidence:
85
Support Request:
0
|
keep open | Migrate linting commands to the shared Craft Application Linter Service to unify UX and eliminate code duplication across craft apps; currently triaged and awaiting assignment after 144 days of inactivity. |
| 2026-06-15 12:46:19.720735+00:00 | pending | — | — | — |