greprag 5.78.0 → 5.78.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.
- package/package.json +1 -1
- package/skill/greprag/SKILL.md +27 -3
package/package.json
CHANGED
package/skill/greprag/SKILL.md
CHANGED
|
@@ -1,16 +1,17 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: greprag
|
|
3
3
|
description: |
|
|
4
|
-
GrepRAG — agentic setup
|
|
4
|
+
GrepRAG — local settings app, agentic setup, and episodic project memory.
|
|
5
5
|
|
|
6
6
|
Single entry point. Runs `greprag status` to learn what's configured,
|
|
7
7
|
walks the user through any missing setup (email signup, hooks, project
|
|
8
8
|
anchor), then either searches the project's memory for the operator's
|
|
9
|
-
topic (`greprag memory search "
|
|
9
|
+
topic (`greprag memory search "query"`) or surfaces the recap
|
|
10
10
|
(`greprag memory recap`) for an open-ended catch-up.
|
|
11
11
|
|
|
12
12
|
Use when: "/greprag", "set up greprag", "greprag status", "configure
|
|
13
|
-
memory", "
|
|
13
|
+
memory", "open greprag", "greprag settings", "settings dashboard",
|
|
14
|
+
"turn GrepRAG on or off", "corpus health", "memory recap", "memory search", "Odyssey briefing", "catch me
|
|
14
15
|
up", "what did we do last week", "what's been happening in this
|
|
15
16
|
project", "find that bug we hit", "search memory for X", "session
|
|
16
17
|
context", "Codex chip", "chip spawn", "spawn a Codex task", "parallel
|
|
@@ -26,6 +27,29 @@ license: MIT
|
|
|
26
27
|
|
|
27
28
|
Single source of truth: `greprag status --json`. Check it → fix any gaps via `docs/setup.md` → search or recap the project's memory.
|
|
28
29
|
|
|
30
|
+
## Local settings app
|
|
31
|
+
|
|
32
|
+
When the user asks to open, inspect, or change GrepRAG settings, launch the
|
|
33
|
+
local app. It owns feature controls, project selection, skills, corpus health,
|
|
34
|
+
agent connections, notifications, privacy, and local runtime diagnostics.
|
|
35
|
+
|
|
36
|
+
```bash
|
|
37
|
+
greprag
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
**WORKING INSIDE THE GREPRAG SOURCE CHECKOUT? USE THE BUILT CHECKOUT, NOT THE
|
|
41
|
+
INSTALLED NPM COMMAND.** Build after source changes, then launch the local CLI
|
|
42
|
+
entrypoint and keep that process alive while the browser is open:
|
|
43
|
+
|
|
44
|
+
```powershell
|
|
45
|
+
npm run build
|
|
46
|
+
node C:\greprag\packages\cli\dist\index.js
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
The bare `greprag` command exercises the globally installed release. Do not
|
|
50
|
+
tell a GrepRAG developer to reinstall NPM merely to inspect unpublished local
|
|
51
|
+
UI changes. For headless use, append `app --no-open` and open its one-time URL.
|
|
52
|
+
|
|
29
53
|
Platform setup is progressive:
|
|
30
54
|
- **Codex**: see `docs/setup.md § codex` after install (`greprag init --codex --tenant-id <handle>`, then Codex Desktop Settings -> Settings -> Hooks trust review).
|
|
31
55
|
- **Claude Code**: see `docs/setup.md § claude-code` for the default hook/Monitor/conventions path (`greprag init --claude` or detected `greprag init`).
|