awesome-claude-code
awesome-claude-code helps with the discovery stage of choosing tools for Claude Code. If a team wants better session memory, a testing workflow or a plugin, a categorized collection gives it somewhere to start. The adoption decision still belongs to the team, using the individual project's implementation, documentation and supported environment.
Our recommendation is to use this collection to produce a small shortlist. Its entries do not form a single software distribution with shared compatibility, licensing or acceptance tests. We audited the directory itself and visited six sampled destinations. We did not install any listed skill, plugin, client or MCP server.
On November 4, 2026, we fixed the upstream revision at a4600018e7cb6282cceae22cd9a354c6cf548a98. The audit reads the README, resource CSV, contribution guide and license. It checks their SHA-256 fingerprints before calculating results, so a future revision cannot silently inherit this snapshot's numbers.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-10
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 0
- Latest release
- —
- Open issues
- 1237
- Recent issues with at least one comment
- 29/30
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #391 [Resource]: Autospec - CLI for Spec Driven Development8 comments · 2025-12-17
- #2096 [Resource]: Claude Supercharger7 comments · 2026-06-22
- #1546 [Resource]: clockwork: a temporal awareness plugin for Claude7 comments · 2026-04-14
- #387 [Enhancement]: Handle unmaintained projects7 comments · 2025-12-17
- #1474 [RESOURCE]: claude-music6 comments · 2026-04-10
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You need a small category-based shortlist of Claude Code resources.
- You can evaluate each selected project at a specific version in your own environment.
- You expect a single installable distribution with shared compatibility guarantees.
- You need an audited production recommendation without investigating individual projects.
Compatibility
Use cases
Alternatives
Comments
No comments yet. Be the first!