@drunkcoding/agents-and-skills 0.0.26 → 0.0.28

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.
@@ -12,7 +12,7 @@
12
12
  "name": "tech-graph",
13
13
  "source": "./plugins/tech-graph",
14
14
  "description": "6-step wizard for technical diagrams (SVG/PNG) via fireworks-tech-graph",
15
- "version": "0.0.26",
15
+ "version": "0.0.28",
16
16
  "category": "diagram",
17
17
  "keywords": [
18
18
  "diagram",
@@ -26,7 +26,7 @@
26
26
  "name": "html-effectiveness",
27
27
  "source": "./plugins/html-effectiveness",
28
28
  "description": "Generate self-contained interactive HTML reports from 20 upstream templates via a conversational agent.",
29
- "version": "0.0.26",
29
+ "version": "0.0.28",
30
30
  "category": "reports",
31
31
  "keywords": [
32
32
  "html",
@@ -41,7 +41,7 @@
41
41
  "name": "plugin-validator",
42
42
  "source": "./plugins/plugin-validator",
43
43
  "description": "Orchestrated validator for Claude Code plugins — validates skills, agents, commands, and hooks across every plugin under plugins/**.",
44
- "version": "0.0.26",
44
+ "version": "0.0.28",
45
45
  "category": "tooling",
46
46
  "keywords": [
47
47
  "validation",
@@ -57,7 +57,7 @@
57
57
  "name": "team-share",
58
58
  "source": "./plugins/team-share",
59
59
  "description": "Share Claude plugin settings with a team, scaffold CLAUDE.md when needed, refresh the Understand-Anything graph, and stage the onboarding artifacts for review.",
60
- "version": "0.0.26",
60
+ "version": "0.0.28",
61
61
  "category": "tooling",
62
62
  "keywords": [
63
63
  "onboarding",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@drunkcoding/agents-and-skills",
3
- "version": "0.0.26",
3
+ "version": "0.0.28",
4
4
  "description": "Personal collection of Claude Code skills and agents, installable via `npx skills`.",
5
5
  "keywords": [
6
6
  "claude-code",
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "html-effectiveness",
3
3
  "displayName": "HTML Effectiveness Reports",
4
- "version": "0.0.26",
4
+ "version": "0.0.28",
5
5
  "description": "Generate self-contained interactive HTML reports from 20 upstream templates via a conversational agent.",
6
6
  "author": {
7
7
  "name": "Steven Hoang"
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "plugin-validator",
3
3
  "displayName": "Plugin Validator",
4
- "version": "0.0.26",
4
+ "version": "0.0.28",
5
5
  "description": "Orchestrated validator for Claude Code plugins — validates skills, agents, commands, and hooks across every plugin under plugins/**.",
6
6
  "author": {
7
7
  "name": "Steven Hoang"
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "team-share",
3
3
  "displayName": "Team Share",
4
- "version": "0.0.26",
4
+ "version": "0.0.28",
5
5
  "description": "Share Claude plugin settings with a team, scaffold CLAUDE.md when needed, refresh the Understand-Anything graph, and stage the onboarding artifacts for review.",
6
6
  "author": {
7
7
  "name": "Steven Hoang"
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: team-share
3
- description: Share Claude plugin settings with the team, build or refresh the Understand-Anything knowledge graph with auto-update, and git-lfs track it before staging everything for review.
3
+ description: Share Claude plugin settings with the team, build or refresh the Understand-Anything knowledge graph, initialize the docs wiki, and git-lfs track it before staging everything for review.
4
4
  argument-hint: "[--force] [--language <lang>] (passed through to /understand)"
5
5
  allowed-tools: Bash, Read, Write, Edit, Glob, Grep, Skill
6
6
  ---
@@ -11,7 +11,8 @@ Make this repo onboarding-ready for the team in one pass:
11
11
 
12
12
  1. Generate a **shareable `.claude/settings.json`** (plugins + marketplaces) from the maintainer's live setup.
13
13
  2. Build/refresh the **Understand-Anything knowledge graph** with auto-update enabled.
14
- 3. **git-lfs track** the graph and **stage** everything leaving the commit to a human.
14
+ 3. Initialize the **docs wiki** for Understand-Anything under `docs/wiki`.
15
+ 4. **git-lfs track** the graph and **stage** everything — leaving the commit to a human.
15
16
 
16
17
  This command is **idempotent** — safe to re-run. It **never commits or pushes**; it only stages.
17
18
  `$ARGUMENTS` (e.g. `--force`, `--language zh`) is forwarded to `/understand`.
@@ -40,7 +41,7 @@ Goal: teammates who clone the repo get the **same plugins + marketplaces** the m
40
41
 
41
42
  ### 1a — Merge plugin + marketplace settings
42
43
 
43
- Copy **only** `enabledPlugins` and `extraKnownMarketplaces` from the maintainer's user settings into the repo settings. Do **NOT** copy `hooks`, `permissions`, `env`, or any key holding absolute paths or local tooling (those are per-machine and may expose private paths).
44
+ Copy **only** `enabledPlugins` and `extraKnownMarketplaces` from the maintainer's user settings into the repo settings. Do **NOT** copy `hooks`, `permissions`, `env`, or any key holding absolute paths or machine-local secrets.
44
45
 
45
46
  ```bash
46
47
  USER_SETTINGS="$HOME/.claude/settings.json"
@@ -70,7 +71,7 @@ Notes:
70
71
 
71
72
  ### 1b — Scaffold `CLAUDE.md` if missing
72
73
 
73
- The `claude-code-setup` plugin (from the `claude-plugins-official` marketplace) generates a project-savvy `CLAUDE.md` when one does not yet exist. Running the install command is **idempotent** — if `CLAUDE.md` is already present it will **not** be overwritten.
74
+ The `claude-code-setup` plugin (from the `claude-plugins-official` marketplace) generates a project-savvy `CLAUDE.md` when one does not yet exist. Running the install command is **idempotent** — if the file already exists, this step is skipped.
74
75
 
75
76
  ```bash
76
77
  # Only create CLAUDE.md when it does not already exist.
@@ -91,6 +92,71 @@ Notes:
91
92
  - The plugin must already be available in the `claude-plugins-official` marketplace (it is already listed in `enabledPlugins` in the repo settings).
92
93
  - If the team prefers a custom `CLAUDE.md` template, commit one *before* running this command so the guard `[ -f CLAUDE.md ]` skips the plugin step.
93
94
 
95
+ ### 1c — Inject the Understand-Anything code-research section into `CLAUDE.md`
96
+
97
+ Goal: every teammate's AI assistant knows to use the Understand-Anything commands when doing code research, without duplicating the section on re-runs.
98
+
99
+ ```bash
100
+ # Only append when the section marker is not already present (idempotent).
101
+ if grep -qF '## Code research with Understand-Anything' CLAUDE.md 2>/dev/null; then
102
+ echo "✅ Understand-Anything section already in CLAUDE.md — skipping."
103
+ else
104
+ cat >> CLAUDE.md << 'EOF'
105
+
106
+ ## Code research with Understand-Anything
107
+
108
+ This project uses the [Understand-Anything](https://github.com/Egonex-AI/Understand-Anything) plugin to maintain an interactive knowledge graph of the codebase. **Always prefer these commands over raw file-by-file exploration when doing code research:**
109
+
110
+ | Goal | Command |
111
+ |------|---------|
112
+ | Explore the full codebase graph | `/understand` |
113
+ | Ask a free-form question about the code | `/understand-chat <question>` |
114
+ | Deep-dive into a specific file or function | `/understand-explain <path/symbol>` |
115
+ | See impact of your current changes before committing | `/understand-diff` |
116
+ | Open the interactive visual dashboard | `/understand-dashboard` |
117
+ | Extract business-domain knowledge (domains, flows, steps) | `/understand-domain` |
118
+ | Generate an onboarding guide for new teammates | `/understand-onboard` |
119
+ | Generate or refresh wiki knowledge under `docs/wiki` | `/understand-knowledge docs/wiki` |
120
+
121
+ The knowledge graph lives in `.understand-anything/knowledge-graph.json` and is kept up-to-date automatically on every commit (auto-update is enabled). Re-run `/understand` after large refactors to force the graph to catch up, and re-run `/understand-knowledge docs/wiki` when you want to refresh the generated wiki content.
122
+ EOF
123
+ echo "✅ Understand-Anything code-research section appended to CLAUDE.md."
124
+ fi
125
+ ```
126
+
127
+ Notes:
128
+ - The section is appended at the end of `CLAUDE.md` so it does not disturb existing content.
129
+ - The marker string `## Code research with Understand-Anything` is used as the idempotency guard — do not rename the heading without updating the guard.
130
+ - If `MIRRORS.md` / `AGENTS.md` or other agent-config files exist alongside `CLAUDE.md` (e.g. for non-Claude runtimes), apply the same append to them so all agent runtimes get the guidance. The loop below appends the same section only when missing.
131
+
132
+ ```bash
133
+ # Mirror to AGENTS.md / MIRRORS.md if they exist (non-Claude runtimes).
134
+ for f in AGENTS.md MIRRORS.md; do
135
+ if [ -f "$f" ] && ! grep -qF '## Code research with Understand-Anything' "$f" 2>/dev/null; then
136
+ cat >> "$f" << 'EOF'
137
+
138
+ ## Code research with Understand-Anything
139
+
140
+ This project uses the [Understand-Anything](https://github.com/Egonex-AI/Understand-Anything) plugin to maintain an interactive knowledge graph of the codebase. **Always prefer these commands over raw file-by-file exploration when doing code research:**
141
+
142
+ | Goal | Command |
143
+ |------|---------|
144
+ | Explore the full codebase graph | `/understand` |
145
+ | Ask a free-form question about the code | `/understand-chat <question>` |
146
+ | Deep-dive into a specific file or function | `/understand-explain <path/symbol>` |
147
+ | See impact of your current changes before committing | `/understand-diff` |
148
+ | Open the interactive visual dashboard | `/understand-dashboard` |
149
+ | Extract business-domain knowledge (domains, flows, steps) | `/understand-domain` |
150
+ | Generate an onboarding guide for new teammates | `/understand-onboard` |
151
+ | Generate or refresh wiki knowledge under `docs/wiki` | `/understand-knowledge docs/wiki` |
152
+
153
+ The knowledge graph lives in `.understand-anything/knowledge-graph.json` and is kept up-to-date automatically on every commit (auto-update is enabled). Re-run `/understand` after large refactors to force the graph to catch up, and re-run `/understand-knowledge docs/wiki` when you want to refresh the generated wiki content.
154
+ EOF
155
+ echo "✅ Understand-Anything section also appended to $f."
156
+ fi
157
+ done
158
+ ```
159
+
94
160
  ---
95
161
 
96
162
  ## Step 2 — Build / refresh the knowledge graph (auto-update on)
@@ -101,13 +167,31 @@ Run the skill **in the main thread** (it dispatches its own analyzer subagents
101
167
  /understand --auto-update $ARGUMENTS
102
168
  ```
103
169
 
104
- - `--auto-update` writes `{"autoUpdate": true}` to `.understand-anything/config.json`. The plugin's bundled hook then incrementally patches the graph whenever a `git commit` is made (and on stale SessionStart), so each commit lands with a matching graph.
170
+ - `--auto-update` writes `{"autoUpdate": true}` to `.understand-anything/config.json`. The plugin's bundled hook then incrementally patches the graph whenever a `git commit` is made (and on stale Session resume, depending on the plugin version).
105
171
  - If a graph already exists, `/understand` runs incrementally. Pass `--force` (via `$ARGUMENTS`) to rebuild from scratch.
106
172
  - After it finishes, confirm these exist: `.understand-anything/knowledge-graph.json`, `.understand-anything/meta.json`, `.understand-anything/config.json` (with `autoUpdate: true`).
107
173
 
108
174
  ---
109
175
 
110
- ## Step 3 — Ignore scratch, git-lfs track the graph, and stage
176
+ ## Step 3 — Initialize the docs wiki from Understand-Anything
177
+
178
+ Create the wiki folder if needed, then generate or refresh the wiki content in the main thread:
179
+
180
+ ```bash
181
+ mkdir -p docs/wiki
182
+ ```
183
+
184
+ ```
185
+ /understand-knowledge docs/wiki
186
+ ```
187
+
188
+ - `mkdir -p docs/wiki` is idempotent and ensures the target directory exists before wiki generation.
189
+ - Re-running `/understand-knowledge docs/wiki` should refresh the generated wiki content in place.
190
+ - After it finishes, confirm `docs/wiki/` exists and contains generated wiki files before staging.
191
+
192
+ ---
193
+
194
+ ## Step 4 — Ignore scratch, git-lfs track the graph, and stage
111
195
 
112
196
  Scratch outputs must stay local (never committed):
113
197
 
@@ -122,7 +206,9 @@ git lfs install
122
206
  git lfs track ".understand-anything/*.json"
123
207
 
124
208
  # Stage — but DO NOT commit. A human reviews and commits.
125
- git add .gitattributes .gitignore .claude/settings.json .understand-anything/
209
+ git add .gitattributes .gitignore .claude/settings.json .understand-anything/ docs/wiki/ CLAUDE.md
210
+ # Also stage AGENTS.md / MIRRORS.md if they were modified.
211
+ for f in AGENTS.md MIRRORS.md; do [ -f "$f" ] && git add "$f"; done
126
212
 
127
213
  git status
128
214
  git lfs ls-files # confirm the graph json is LFS-tracked
@@ -134,7 +220,9 @@ git lfs ls-files # confirm the graph json is LFS-tracked
134
220
 
135
221
  Summarize for the user:
136
222
  - Which plugins/marketplaces were written into `.claude/settings.json` (call out any private ones).
137
- - `CLAUDE.md` status: already existed vs created by `claude-code-setup`.
223
+ - `CLAUDE.md` status: already existed vs created by `claude-code-setup`; Understand-Anything section added vs already present.
224
+ - `AGENTS.md` status (if applicable): Understand-Anything section added vs already present / not found.
138
225
  - Graph status: created vs incrementally updated; `autoUpdate` on/off.
226
+ - Wiki status: `docs/wiki` created vs already existed; `/understand-knowledge docs/wiki` run successfully vs failed.
139
227
  - What is staged and confirmed LFS-tracked.
140
- - Remind them: **review, then commit yourself** (e.g. `git commit -m "chore: share team onboarding (claude settings + CLAUDE.md + understand graph)"`). The auto-update hook keeps the graph fresh on every future commit.
228
+ - Remind them: **review, then commit yourself** (e.g. `git commit -m "chore: share team onboarding (claude settings + CLAUDE.md + understand graph + wiki)"`). The auto-update hook keeps the graph fresh on every future commit, and the wiki can be refreshed by re-running `/understand-knowledge docs/wiki` whenever needed.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "tech-graph",
3
- "version": "0.0.26",
3
+ "version": "0.0.28",
4
4
  "description": "Step-by-step wizard for generating technical diagrams as SVG+PNG.",
5
5
  "author": {
6
6
  "name": "steven"