remove-unused-includes vs error-handling
remove-unused-includes and error-handling are both browser automation skills. remove-unused-includes scores higher (87 vs 87 out of 100). error-handling has more GitHub stars (75k), and remove-unused-includes was updated more recently (3 days ago). The table compares them side by side.
| remove-unused-includes | error-handling | |
|---|---|---|
| Score | 87 / 100 | 87 / 100 |
| What it does | Look through a given folder to find and safely remove unused includes specifically for Clang-compiled code (using clang-include-cleaner), verifying that referencing targets compile. | Use when reviewing scripts, client components, bundles, or runtime behavior related to Implement proper error handling. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug. |
| Publisher | Community: chromium | Community: thedaviddias |
| Grades | Maintenance A, Licence A, Quality A | Maintenance A, Licence A, Quality A |
| npm downloads a week | Not on npm | Not on npm |
| Runs | Skill | Skill |
| Works with | Claude Code, Claude apps | Claude Code, Claude apps |
| GitHub stars | 25,092 | 74,518 |
| Last commit | 20 Oct 2026 | 6 Oct 2026 |
| Licence | BSD-3-Clause | MIT |
| Listed since | 20 Oct 2026 | 20 Oct 2026 |
| Install remove-unused-includes | Install error-handling |
Questions
Is remove-unused-includes or error-handling more popular?
error-handling has more GitHub stars: 74,518.
Can I use remove-unused-includes and error-handling together?
Yes. AI assistants can load several skills at once. Install both and the assistant picks the right one for each task.