qa vs remove-unused-includes
qa and remove-unused-includes are both browser automation skills. remove-unused-includes scores higher (84 vs 70 out of 100). remove-unused-includes has more GitHub stars (25k), and remove-unused-includes was updated more recently (2 days ago). The table compares them side by side.
| qa | remove-unused-includes | |
|---|---|---|
| Score | 70 / 100 | 84 / 100 |
| What it does | Exercise the delivered customer journey using real runtime or browser evidence. Use for functional acceptance testing after implementation, including failure paths. | 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. |
| Publisher | Community: suboss87 | Community: chromium |
| 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 | 972 | 25,092 |
| Last commit | 9 Oct 2026 | 20 Oct 2026 |
| Licence | MIT | BSD-3-Clause |
| Listed since | 19 Oct 2026 | 20 Oct 2026 |
| Install qa | Install remove-unused-includes |
Questions
Is qa or remove-unused-includes more popular?
remove-unused-includes has more GitHub stars: 25,092.
Can I use qa and remove-unused-includes together?
Yes. AI assistants can load several skills at once. Install both and the assistant picks the right one for each task.