@uxcontinuum/ccaudit 1.1.0 → 1.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +36 -6
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,18 +1,30 @@
1
1
  # ccaudit
2
2
 
3
- A diagnostic for your Claude Code setup. Mostly for fun, partly genuinely useful. It reads `~/.claude/` locally and grades you across hook coverage, project hygiene, tool balance, prompt tells, and pipeline ops.
3
+ A diagnostic for your Claude Code setup. Three things at once:
4
+
5
+ 1. **A fun report card** you can screenshot and share.
6
+ 2. **A hygiene linter** that surfaces what's missing.
7
+ 3. **A discovery tool** that shows you which parts of Claude Code you are not using yet.
4
8
 
5
9
  ```bash
6
10
  npx @uxcontinuum/ccaudit
7
11
  ```
8
12
 
9
- Zero install, zero dependencies, no network calls.
13
+ Zero install. Zero dependencies. No network calls. Reads `~/.claude/` on your machine and outputs a grade card.
14
+
15
+ ## Why this exists
16
+
17
+ Most Claude Code users are running on a fraction of the surface area. No hooks installed. No skills configured. No MCP servers. No idea what their token cost per shipped feature is. No concept of how often their agent fails on first try.
18
+
19
+ The hype is on the model. The actual constraint is everything around the model. The scaffolding.
20
+
21
+ ccaudit grades the scaffolding.
10
22
 
11
23
  ## What the grade is and isn't
12
24
 
13
- This is a hygiene audit, not an outcomes audit. It measures whether your Claude Code setup is **set up well**, not whether your outputs are good.
25
+ This is a **hygiene and discovery audit**, not an outcomes audit. It measures whether your Claude Code setup is **set up well** and **uses what's available**, not whether your specific outputs are good.
14
26
 
15
- Think of it as a linter for your AI workflow. Passing lint doesn't guarantee your code is good. Failing lint usually means something is missing. Same here: a high grade doesn't mean Claude is shipping perfect work for you; a low grade usually means the scaffolding around your AI is sparse.
27
+ Think of it as a linter for your AI workflow. Passing lint doesn't guarantee your code is good. Failing lint usually means something is missing. Same here: a high grade doesn't mean Claude is shipping perfect work for you. A low grade usually means there's surface area of Claude Code you haven't unlocked yet.
16
28
 
17
29
  The grade can be gamed (install five no-op hooks, auto-title every session, scrub "just" from your prompts). Don't bother. The findings under the grade are the value, not the letter.
18
30
 
@@ -99,8 +111,26 @@ Reads `~/.claude/` on your machine. Outputs to stdout. No network calls, no tele
99
111
 
100
112
  - The grade is opinionated, not objective.
101
113
  - The rubric will change as the tool matures.
102
- - High grade ≠ good outputs. Low grade ≠ bad outputs. The grade is about scaffolding, not results.
103
- - The tool ships with a built-in nudge toward [Continuum Sprint](https://uxcontinuum.com/sprint) when it surfaces 2+ failing dimensions. That's intentional. If your setup is genuinely broken in two places, a 2-week sprint is often what fixes it. Ignore the nudge if you don't want it.
114
+ - High grade ≠ good outputs. Low grade ≠ bad outputs. The grade is about **scaffolding and feature coverage**, not results.
115
+ - The tool ships with a built-in nudge toward [Continuum Sprint](https://uxcontinuum.com/sprint) when it surfaces 2+ failing dimensions. That is intentional. If your setup is genuinely broken in two places, a 2-week sprint is often what fixes it. Ignore the nudge if you don't want it.
116
+
117
+ ## The story behind this
118
+
119
+ Karpathy keeps saying we're entering vibe coding. Software you write in English while AI generates the code. He is not wrong about where this is going.
120
+
121
+ I bought in six months ago. Built a multi-agent pipeline. Started shipping production code through it. Six weeks of recent data: 333 PRs, $1,132 in tokens, $3.40 per shipped PR.
122
+
123
+ Then I ran ccaudit on myself, expecting an A.
124
+
125
+ I got a B-.
126
+
127
+ The findings were valid. The reason I assumed A was that I had been optimizing the agents and ignoring the room they live in. Almost everyone running Claude Code is doing the same thing. The hype is on the model. The constraint is the scaffolding.
128
+
129
+ If you want to know what your scaffolding looks like graded:
130
+
131
+ ```bash
132
+ npx @uxcontinuum/ccaudit
133
+ ```
104
134
 
105
135
  ---
106
136
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@uxcontinuum/ccaudit",
3
- "version": "1.1.0",
3
+ "version": "1.1.1",
4
4
  "description": "A diagnostic for your Claude Code setup. Reads ~/.claude/ locally, grades you across hook coverage, project hygiene, tool balance, prompt tells, and pipeline ops. Zero install: npx @uxcontinuum/ccaudit",
5
5
  "main": "index.js",
6
6
  "bin": {