@pickled-dev/cli 0.1.0 β†’ 0.2.0

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 (3) hide show
  1. package/README.md +63 -76
  2. package/dist/index.js +217 -108
  3. package/package.json +2 -1
package/README.md CHANGED
@@ -2,122 +2,109 @@
2
2
 
3
3
  > Stay fresh in AI πŸ₯’
4
4
 
5
- Your developer tool is great. But does AI know that?
6
-
7
- Pickled checks how often AI models actually recommend your tool when developers ask questions. Point it at a GitHub repo, and we'll tell you if you're well preservedβ€”or starting to spoil.
5
+ Check if AI recommends your developer tool. Point it at your project, define some discovery scenarios, and see if you're getting picked.
8
6
 
9
7
  ## Installation
10
8
 
11
9
  ```bash
12
- # Global install
13
10
  bun add -g @pickled-dev/cli
14
-
15
- # Or run directly
16
- bunx @pickled-dev/cli check github.com/org/repo
17
11
  ```
18
12
 
19
- You'll need an Anthropic API key:
13
+ ## Usage
14
+
15
+ ### 1. Initialize config
20
16
 
21
17
  ```bash
22
- export ANTHROPIC_API_KEY=your-key-here
18
+ pickled init
23
19
  ```
24
20
 
25
- ## Usage
21
+ Creates a `pickled.yml` file:
26
22
 
27
- ```bash
28
- pickled check <repo>
29
- ```
23
+ ```yaml
24
+ tool:
25
+ name: "your-tool"
26
+ description: "What your tool does"
27
+ keywords:
28
+ - keyword1
29
+ - keyword2
30
+
31
+ scenarios:
32
+ - name: "General discovery"
33
+ prompt: "What's a good library for [your use case]?"
30
34
 
31
- That's it. We'll handle the rest.
35
+ - name: "Specific feature"
36
+ prompt: "I need a tool that can [specific feature]. What should I use?"
37
+ ```
32
38
 
33
- ### Options
39
+ ### 2. Edit your config
34
40
 
35
- | Flag | What it does |
36
- |------|--------------|
37
- | `--json` | Output as fresh JSON |
38
- | `-o, --output <file>` | Save your freshness report (.json or .xml) |
39
- | `-v, --verbose` | Show the full pickling process |
40
- | `-c, --competitors <list>` | Bring your own shelf mates (skip auto-discovery) |
41
+ Update `pickled.yml` with your actual tool info and scenarios that developers might ask.
41
42
 
42
- ### Examples
43
+ ### 3. Run check
43
44
 
44
45
  ```bash
45
- # How fresh is zod?
46
- pickled check github.com/colinhacks/zod
46
+ pickled check
47
+ ```
47
48
 
48
- # Check against specific competitors
49
- pickled check github.com/colinhacks/zod -c "yup,joi,valibot"
49
+ ## Commands
50
50
 
51
- # Save the report
52
- pickled check github.com/colinhacks/zod -o report.json
51
+ ### `pickled init [path]`
53
52
 
54
- # Watch the whole process
55
- pickled check github.com/colinhacks/zod -v
56
- ```
53
+ Create a starter `pickled.yml` config file.
57
54
 
58
- ## What You'll See
55
+ ### `pickled check [path]`
59
56
 
60
- ```
61
- πŸ₯’ Freshness Report: zod
62
- ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
57
+ Run discovery scenarios and report results.
63
58
 
64
- πŸ“¦ What's in the jar: zod - TypeScript-first schema validation
65
- 🏷️ Domain: validation
66
- πŸ«™ Who else is on the shelf: yup, joi, valibot
59
+ | Option | Description |
60
+ | --------------------- | ---------------------- |
61
+ | `--json` | Output as JSON |
62
+ | `-o, --output <file>` | Save report to file |
63
+ | `-v, --verbose` | Show detailed progress |
67
64
 
68
- ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
69
- πŸ“Š HOW FRESH ARE YOU?
65
+ ## Example Output
66
+
67
+ ```
68
+ πŸ₯’ pickled check results
70
69
  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
71
70
 
72
- Topic: "TypeScript validation library"
73
- πŸ₯’ zod: 8/10 (80%) - Well preserved!
74
- β”œβ”€ yup: 5/10 (50%)
75
- └─ joi: 2/10 (20%)
71
+ Tool: zod
72
+ Path: /path/to/zod
76
73
 
77
- Topic: "Runtime type checking"
78
- πŸ₯’ zod: 7/10 (70%) - Well preserved!
79
- β”œβ”€ valibot: 6/10 (60%)
80
- └─ yup: 3/10 (30%)
74
+ βœ“ "Validation library" - passed
75
+ βœ“ "Schema validation" - passed
76
+ βœ— "Form validation" - tool not mentioned
81
77
 
82
78
  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
83
- πŸ“ˆ FRESHNESS SUMMARY
84
- ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
85
-
86
- Overall freshness: 75% - Looking Fresh πŸ₯’
87
- Top of the shelf in: 2/2 topics
79
+ Freshness: 2/3 (67%) πŸ₯’πŸ₯’πŸ₯’β–‘β–‘
88
80
 
89
- πŸ₯’ You're kind of a big dill!
90
- Stay fresh! πŸ₯’
81
+ πŸ₯’ Not bad, but room to get fresher.
91
82
  ```
92
83
 
93
- ## How It Works
84
+ ## Config Reference
94
85
 
95
- 1. **Opens the jar** β€” Fetches your GitHub repo
96
- 2. **Checks what's inside** β€” Extracts product info from README and package.json
97
- 3. **Sees who else is on the shelf** β€” Discovers competitors in your space
98
- 4. **Picks the right questions** β€” Generates topics developers actually ask about
99
- 5. **Checks your freshness** β€” Queries AI with those questions
100
- 6. **Gives you the truth** β€” Reports how often you get picked vs the competition
86
+ ```yaml
87
+ tool:
88
+ name: "tool-name" # Required: your tool's name
89
+ description: "description" # Required: what it does
90
+ keywords: # Required: relevant keywords
91
+ - keyword1
92
+ - keyword2
101
93
 
102
- ## Why This Matters
94
+ scenarios: # Required: discovery scenarios
95
+ - name: "Scenario name" # Display name
96
+ prompt: "The question" # What to ask AI
103
97
 
104
- AI assistants are becoming the new Stack Overflow. When a developer asks "what's the best validation library?", you want to be the answer.
105
-
106
- If you're not getting recommended, your visibility is spoiling. Time to do something about it.
98
+ runner: # Optional: customize AI runner
99
+ model: claude-sonnet-4-20250514
100
+ maxTurns: 3
101
+ ```
107
102
 
108
103
  ## Local Development
109
104
 
110
105
  ```bash
111
106
  # From the monorepo root
112
107
  bun install
113
-
114
- # Copy the example env file and add your API key
115
- cp apps/cli/.env.example .env
116
-
117
- # Run the CLI
118
- bun dev:cli check github.com/org/repo
108
+ bun run dev:cli -- init
109
+ bun run dev:cli -- check
119
110
  ```
120
-
121
- ---
122
-
123
- Built with πŸ₯’ by the Pickled team