You can 'record' yourself using a website - and Chrome records how many 'hits' each css rule gets.
This is better than Dust-me, and all the other CSS rule detectors - because it allows you to use your site in a 'dynamic' way - and test for all the edge CSS cases (like resizing your browser to small, or enabling an error message etc).
After using my SaaS for an hour - I found hundreds of rules that just never got used.
Also - it tells you how many times a rule got used. So I found a few number of rules that literally only got used once, and I could often re-write them into 1-2 bigger rules - further reducing my CSS overhead.
Hopefully this is indicative of the quality of this library! I'll definitely try it out this morning.
Maybe the project should be named "cs"? :)
> I connect stuff and copy bits. Sometimes it doesn't work
Stay away from the RedundancyAnalyzer though. There be dragons.
 https://github.com/begriffs/css-ratiocinator and http://www.csstrashman.com/
I would think that using mixins should also count as having eliminated redundancy. A simple solution would be to ignore them, or more ideally the redundancy check could treat mixins just as a normal rule, so that it could detect using the same set of mixins in multiple places as redundancy.
My initial opinion is that even though your SCSS code is consolidated, the resulting CSS code is still duplicated all over the place. To me, that is a code smell. Particularly when I need to debug from the web developer tools.
But, one issue. It appears to not support @import of Compass extensions: "File to import not found or unreadable."
This may also be of interest:
Dust-Me Selectors is a firefox extension that scans HTML pages to find unused CSS selectors. http://www.brothercake.com/dustmeselectors/