Editor/IDE/linting support for deleting dead css

Css-blocks seems really awesome, and on further investigation, I think it will be the GOTO solution for css once it has reached 1.0 status

One thing I am curious about - I know css blocks will remove unused css - this is awesome so your utility classes can be there if you need them, but don't cause un-necessary bloat.

However, if you are refactoring large amounts of css, it seems to me we'd also be interested in removing the code from the codebase altogether. The best solution in my eyes would be an editor/ide extension that highlights unused/dead css, along with a linter that can help you clean up the whole codebase or evaluate its cleanliness.

Will this eventually be something that's included in the css-blocks experience?

The issue names no files, tests, or entry points; first inspect the repository structure and existing CSS-blocks tooling before defining the scope. Clarify whether the desired result is an editor/IDE extension, a linter, or both, and agree on how unused CSS should be detected and what a completed implementation must demonstrate.

Written by the indexing model from the issue text.