@viberaven/cli 1.0.1 → 1.0.3
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.
- package/AGENTS.md +71 -6
- package/README.md +10 -10
- package/SECURITY.md +4 -4
- package/dist/cli.js +343 -40
- package/dist/cli.js.map +4 -4
- package/package.json +1 -1
- package/templates/AGENTS.snippet.md +10 -10
- package/templates/CLAUDE.snippet.md +5 -5
- package/templates/CURSOR.snippet.md +5 -5
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@viberaven/cli",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.3",
|
|
4
4
|
"description": "Production-readiness scan for AI-built apps: auth, billing, database, deployment, monitoring, launch gaps, and agent-ready fixes.",
|
|
5
5
|
"license": "UNLICENSED",
|
|
6
6
|
"author": "VibeRaven",
|
|
@@ -7,7 +7,7 @@ Use VibeRaven when the user asks if their AI-built app is production-ready, laun
|
|
|
7
7
|
### Humans
|
|
8
8
|
|
|
9
9
|
```bash
|
|
10
|
-
npx -y
|
|
10
|
+
npx -y viberaven
|
|
11
11
|
```
|
|
12
12
|
|
|
13
13
|
In a real terminal, this opens the interactive VibeRaven menu.
|
|
@@ -17,32 +17,32 @@ In a real terminal, this opens the interactive VibeRaven menu.
|
|
|
17
17
|
Paste this into your coding agent:
|
|
18
18
|
|
|
19
19
|
```bash
|
|
20
|
-
npx -y
|
|
20
|
+
npx -y viberaven --agent-mode
|
|
21
21
|
```
|
|
22
22
|
|
|
23
|
-
1. Run `npx -y
|
|
23
|
+
1. Run `npx -y viberaven --agent-mode` from the project root.
|
|
24
24
|
2. If VibeRaven prints `LOGIN_URL_READY`, open that exact URL for the user. Say: "I opened VibeRaven sign-in so you can approve access; I will continue after approval." Do not ask for passwords, tokens, cookies, or secrets. Keep the terminal alive while the user approves.
|
|
25
|
-
If the scan flow cannot start login, run `npx -y
|
|
25
|
+
If the scan flow cannot start login, run `npx -y viberaven login`.
|
|
26
26
|
3. Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context. If the tasklist says `CRITICAL GAPS DETECTED` or `PRODUCTION GATE NOT CLEAR`, fix one listed repo-code gap before deploy.
|
|
27
27
|
4. Read `.viberaven/agent-summary.md` second for scan context.
|
|
28
28
|
5. Read `.viberaven/launch-playbook.md` third for the full checklist.
|
|
29
|
-
6. Use `npx -y
|
|
30
|
-
7. For Vercel + Supabase, run `npx -y
|
|
29
|
+
6. Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix. Local installs can use `viberaven prompt`.
|
|
30
|
+
7. For Vercel + Supabase, run `npx -y viberaven audit --vercel-supabase` and check RLS, service role exposure, and Supabase pooler port 6543 instead of runtime port 5432.
|
|
31
31
|
8. Do not claim provider dashboard checks are fixed by repo-code edits.
|
|
32
|
-
9. Verify with tests/build, then run `npx -y
|
|
32
|
+
9. Verify with tests/build, then run `npx -y viberaven --verify`.
|
|
33
33
|
|
|
34
34
|
Before deploy or CI pass:
|
|
35
35
|
|
|
36
36
|
```bash
|
|
37
|
-
npx -y
|
|
37
|
+
npx -y viberaven --strict
|
|
38
38
|
```
|
|
39
39
|
|
|
40
40
|
Also available:
|
|
41
41
|
|
|
42
42
|
- `.viberaven/last-scan.json` - full mission map and gaps
|
|
43
43
|
- `.viberaven/report.html` - visual map for the user
|
|
44
|
-
- `npx -y
|
|
45
|
-
- `npx -y
|
|
44
|
+
- `npx -y viberaven init --dry-run` - preview local agent rules
|
|
45
|
+
- `npx -y viberaven clean --plan` - write a non-destructive cleanup plan
|
|
46
46
|
|
|
47
47
|
Free plan: 2 lifetime scans, 6/12 mission map lanes. Pro: 50 scans/month, all 12 lanes.
|
|
48
48
|
|
|
@@ -3,14 +3,14 @@
|
|
|
3
3
|
|
|
4
4
|
VibeRaven is the Agent Context + Production Gate.
|
|
5
5
|
|
|
6
|
-
- When production readiness, launch readiness, Vercel, Supabase, auth, database, payments, monitoring, deployment, rate limits, or error handling comes up, run `npx -y
|
|
6
|
+
- When production readiness, launch readiness, Vercel, Supabase, auth, database, payments, monitoring, deployment, rate limits, or error handling comes up, run `npx -y viberaven --agent-mode` from the project root.
|
|
7
7
|
- Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context.
|
|
8
8
|
- Read `.viberaven/agent-summary.md` before editing code.
|
|
9
9
|
- Read `.viberaven/launch-playbook.md` before editing code.
|
|
10
|
-
- Use `npx -y
|
|
11
|
-
- Run `npx -y
|
|
12
|
-
- Run `npx -y
|
|
13
|
-
- For Vercel + Supabase launch checks, run `npx -y
|
|
10
|
+
- Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
|
|
11
|
+
- Run `npx -y viberaven --verify` after one fix.
|
|
12
|
+
- Run `npx -y viberaven --strict` before deploy or CI pass.
|
|
13
|
+
- For Vercel + Supabase launch checks, run `npx -y viberaven audit --vercel-supabase`.
|
|
14
14
|
- Do not claim provider dashboard work is fixed by repo-code edits. Provider dashboard checks, billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must be completed or verified in the provider dashboard.
|
|
15
15
|
- If VibeRaven prints `LOGIN_URL_READY`, open that URL for the user using the available browser tool or system browser. Tell the user: "I opened VibeRaven sign-in so you can approve access; I will continue after approval." Do not ask for passwords, tokens, cookies, or secrets. Keep the terminal process alive while the user approves.
|
|
16
16
|
<!-- viberaven:agent-rules:end -->
|
|
@@ -3,14 +3,14 @@
|
|
|
3
3
|
|
|
4
4
|
VibeRaven is the Agent Context + Production Gate.
|
|
5
5
|
|
|
6
|
-
- When production readiness, launch readiness, Vercel, Supabase, auth, database, payments, monitoring, deployment, rate limits, or error handling comes up, run `npx -y
|
|
6
|
+
- When production readiness, launch readiness, Vercel, Supabase, auth, database, payments, monitoring, deployment, rate limits, or error handling comes up, run `npx -y viberaven --agent-mode` from the project root.
|
|
7
7
|
- Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context.
|
|
8
8
|
- Read `.viberaven/agent-summary.md` before editing code.
|
|
9
9
|
- Read `.viberaven/launch-playbook.md` before editing code.
|
|
10
|
-
- Use `npx -y
|
|
11
|
-
- Run `npx -y
|
|
12
|
-
- Run `npx -y
|
|
13
|
-
- For Vercel + Supabase launch checks, run `npx -y
|
|
10
|
+
- Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
|
|
11
|
+
- Run `npx -y viberaven --verify` after one fix.
|
|
12
|
+
- Run `npx -y viberaven --strict` before deploy or CI pass.
|
|
13
|
+
- For Vercel + Supabase launch checks, run `npx -y viberaven audit --vercel-supabase`.
|
|
14
14
|
- Do not claim provider dashboard work is fixed by repo-code edits. Provider dashboard checks, billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must be completed or verified in the provider dashboard.
|
|
15
15
|
- If VibeRaven prints `LOGIN_URL_READY`, open that URL for the user using the available browser tool or system browser. Tell the user: "I opened VibeRaven sign-in so you can approve access; I will continue after approval." Do not ask for passwords, tokens, cookies, or secrets. Keep the terminal process alive while the user approves.
|
|
16
16
|
<!-- viberaven:agent-rules:end -->
|