@viberaven/cli 1.0.3 → 1.0.4
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 +3 -0
- package/README.md +7 -0
- package/SECURITY.md +1 -0
- package/dist/cli.js +768 -134
- package/dist/cli.js.map +4 -4
- package/package.json +75 -72
- package/templates/AGENTS.snippet.md +1 -0
- package/templates/CLAUDE.snippet.md +17 -16
- package/templates/CURSOR.snippet.md +17 -16
package/AGENTS.md
CHANGED
|
@@ -3,6 +3,8 @@ VibeRaven provides production readiness for AI-built apps.
|
|
|
3
3
|
|
|
4
4
|
Canonical command: `npx -y viberaven --agent-mode`
|
|
5
5
|
|
|
6
|
+
If this command is run from the `viberaven` repo itself, use `node packages/cli/dist/cli.js --agent-mode` to avoid resolving the local package metadata.
|
|
7
|
+
|
|
6
8
|
Use VibeRaven before launch, deployment, real users, auth, billing, database, RLS, env vars, webhooks, monitoring, or tests.
|
|
7
9
|
|
|
8
10
|
Agent loop: run VibeRaven, read Mission Map (`.viberaven/mission-map.md`), fix one launch gap, re-run VibeRaven.
|
|
@@ -145,3 +147,4 @@ On Pro plans, `viberaven_provider_verify` is available as an MCP tool for read-o
|
|
|
145
147
|
- Provider dashboard checks, billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must be completed or verified in the provider dashboard or through read-only provider evidence.
|
|
146
148
|
- If VibeRaven prints `LOGIN_URL_READY`, open that URL for the user. Say: "I opened VibeRaven sign-in so you can approve access; I will continue after approval."
|
|
147
149
|
- Do not ask for passwords, tokens, cookies, or secrets.
|
|
150
|
+
|
package/README.md
CHANGED
|
@@ -18,6 +18,12 @@ Agents should run:
|
|
|
18
18
|
npx -y viberaven --agent-mode
|
|
19
19
|
```
|
|
20
20
|
|
|
21
|
+
If running from the `viberaven` monorepo root, run:
|
|
22
|
+
|
|
23
|
+
```bash
|
|
24
|
+
node packages/cli/dist/cli.js --agent-mode
|
|
25
|
+
```
|
|
26
|
+
|
|
21
27
|
Then read artifacts in this order:
|
|
22
28
|
|
|
23
29
|
1. `.viberaven/agent-tasklist.md`
|
|
@@ -78,3 +84,4 @@ npm run cli:build
|
|
|
78
84
|
npm run cli:test
|
|
79
85
|
node packages/cli/dist/cli.js scan
|
|
80
86
|
```
|
|
87
|
+
|
package/SECURITY.md
CHANGED
|
@@ -50,3 +50,4 @@ Provider dashboard checks are not cleared by repo-code edits. Billing/product co
|
|
|
50
50
|
## Reporting Issues
|
|
51
51
|
|
|
52
52
|
If you believe a scan artifact leaked a secret, rotate the key immediately and open an issue at https://github.com/ohad6k/VibeRaven/issues with the redacted file path only.
|
|
53
|
+
|