@codihaus/claude-skills 1.6.10 → 1.6.11

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 CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@codihaus/claude-skills",
3
- "version": "1.6.10",
3
+ "version": "1.6.11",
4
4
  "description": "Claude Code skills for software development workflow",
5
5
  "main": "src/index.js",
6
6
  "bin": {
@@ -22,9 +22,10 @@ Central registry of all available skills. Reference this to suggest relevant ski
22
22
  | Skill | Purpose | Called By |
23
23
  |-------|---------|-----------|
24
24
  | `/utils/diagram` | Create/validate Mermaid diagrams | `/dev-scout`, `/dev-specs`, `/dev-arch` |
25
- | `/utils/docs-graph` | View documentation relationships | `/debrief`, `/dev-specs`, `/dev-arch` |
26
25
  | `/utils/gemini` | Large context scanning (1M tokens) | `/dev-scout` for large codebases |
27
26
 
27
+ **Note:** Documentation graph (`docs-graph.json`) is automatically updated by Claude Code hook, not a skill.
28
+
28
29
  ## Skill Flow
29
30
 
30
31
  ```
@@ -66,9 +67,6 @@ Need to document what was built?
66
67
 
67
68
  Need to visualize something?
68
69
  → /utils/diagram (usually called by other skills)
69
-
70
- Need to see doc relationships?
71
- → /utils/docs-graph (usually called by other skills)
72
70
  ```
73
71
 
74
72
  ## Trigger Phrases
@@ -86,7 +84,6 @@ When user says... → Suggest skill
86
84
  | "review my code", "check this PR" | `/dev-review` |
87
85
  | "what was built", "summarize changes", "document implementation" | `/dev-changelog` |
88
86
  | "create diagram", "architecture diagram", "flow chart" | `/utils/diagram` |
89
- | "what links to this", "doc relationships" | `/utils/docs-graph` |
90
87
 
91
88
  ## Cross-Skill Suggestions
92
89
 
@@ -147,11 +144,6 @@ During each skill, consider suggesting:
147
144
  - Called by other skills, not typically invoked directly
148
145
  - Used for: architecture diagrams, flow charts, ERD
149
146
 
150
- ### /utils/docs-graph
151
- - Utility skill for documentation relationships
152
- - Called by other skills to understand dependencies
153
- - Auto-updated by Claude Code hooks
154
-
155
147
  ## Quality Attributes
156
148
 
157
149
  All skills reference `skills/_quality-attributes.md` for their respective level:
@@ -10,7 +10,7 @@ version: 3.9.0
10
10
  > - **Before**: Use `/dev-scout` if existing codebase
11
11
  > - **During**: Calls `/dev-arch` to validate architecture feasibility
12
12
  > - **After**: Use `/dev-specs` for implementation plans
13
- > - **Utils**: `/utils/docs-graph` for relationships
13
+ > - **Auto**: `docs-graph.json` updated by hook for relationships
14
14
 
15
15
  Create and maintain the unified BRD for a project. Handles initial requirements and feature additions.
16
16
 
@@ -1,177 +0,0 @@
1
- ---
2
- name: utils/docs-graph
3
- description: View and query the documentation knowledge graph
4
- version: 1.3.0
5
- ---
6
-
7
- # /utils/docs-graph - Documentation Graph Viewer
8
-
9
- > **Skill Awareness**: See `skills/_registry.md` for all available skills.
10
- > - **Auto-updated**: By Claude Code hook on Write/Edit to plans/
11
- > - **Called by**: `/dev-specs`, `/debrief`, `/dev-arch` for relationships
12
- > - **Note**: Utility skill, typically called by other skills
13
-
14
- View and query relationships between planning documents.
15
-
16
- ## When to Use
17
-
18
- - See overview of all plans and their relationships
19
- - Find related documents before making changes
20
- - Check impact of changes (what links to this?)
21
- - Verify links are valid
22
-
23
- ## Usage
24
-
25
- ```
26
- /utils/docs-graph # Show graph summary
27
- /utils/docs-graph auth # Show nodes related to "auth"
28
- /utils/docs-graph --check # Verify all links resolve
29
- ```
30
-
31
- ## How It Works
32
-
33
- **Automatic Updates:**
34
- - PostToolUse hook triggers on Write/Edit to `plans/`
35
- - Regenerates entire graph from all files in `plans/`
36
- - Updates `plans/docs-graph.json` and `plans/docs-graph.md`
37
- - Timeout: 3 minutes
38
-
39
- **Graph Files:**
40
- ```
41
- plans/
42
- ├── docs-graph.json # Machine-readable graph data
43
- └── docs-graph.md # Mermaid visualization
44
- ```
45
-
46
- ## Expected Outcome
47
-
48
- **Summary mode (default):**
49
- - Node count by type
50
- - Edge count
51
- - Mermaid diagram from docs-graph.md
52
-
53
- **Query mode (with argument like "auth"):**
54
- - Matching nodes
55
- - Incoming links (what references this)
56
- - Outgoing links (what this references)
57
-
58
- **Check mode (--check):**
59
- - Report broken links
60
- - Suggest fixes
61
-
62
- ## Wikilink Convention
63
-
64
- Documents use `[[wikilinks]]` to reference each other:
65
-
66
- ```markdown
67
- # UC-AUTH-001: Login
68
-
69
- > **Feature**: [[feature-auth]]
70
- > **Related**: [[uc-auth-002]], [[uc-auth-003]]
71
- > **Spec**: [[spec-auth-001]]
72
- ```
73
-
74
- **Link ID format:**
75
- - Use cases: `[[uc-auth-001]]` (lowercase, no slug)
76
- - Features: `[[feature-auth]]`
77
- - Specs: `[[spec-auth-001]]`
78
- - Change requests: `[[cr-001]]`
79
-
80
- ## Node Types
81
-
82
- | Type | Source | Shape (Mermaid) |
83
- |------|--------|-----------------|
84
- | brd | `brd/README.md` | Stadium `[[]]` |
85
- | use-case | `brd/use-cases/**/*.md` | Rectangle `[]` |
86
- | change-request | `brd/changes/*.md` | Hexagon `{{}}` |
87
- | feature | `features/*/README.md` | Pill `([])` |
88
- | spec | `features/*/specs/**/*.md` | Parallelogram `[//]` |
89
- | scout | `**/scout.md` | Cylinder `[()]` |
90
-
91
- ## Example Output
92
-
93
- ### Summary
94
-
95
- ```
96
- Documentation Graph Summary
97
- ===========================
98
- Nodes: 12 | Edges: 18
99
-
100
- By Type:
101
- use-case: 5
102
- feature: 2
103
- spec: 4
104
- brd: 1
105
-
106
- View full graph: plans/docs-graph.md
107
- ```
108
-
109
- ### Query: `/utils/docs-graph auth`
110
-
111
- ```
112
- Nodes matching "auth": 4
113
-
114
- uc-auth-001 (use-case) - Login
115
- ← feature-auth, spec-auth-001
116
- → feature-auth
117
-
118
- uc-auth-002 (use-case) - Signup
119
- ← feature-auth
120
- → uc-auth-001, feature-auth
121
-
122
- feature-auth (feature) - Authentication
123
- ← uc-auth-001, uc-auth-002, uc-auth-003
124
- → (none)
125
-
126
- spec-auth-001 (spec) - Login Spec
127
- ← (none)
128
- → uc-auth-001
129
- ```
130
-
131
- ### Check: `/utils/docs-graph --check`
132
-
133
- ```
134
- Link Check Results
135
- ==================
136
- ✓ 16 valid links
137
- ✗ 2 broken links
138
-
139
- Broken:
140
- plans/brd/use-cases/auth/UC-AUTH-001-login.md:5
141
- [[uc-auth-004]] - node not found
142
-
143
- plans/features/auth/specs/UC-AUTH-001/README.md:12
144
- [[feature-billing]] - node not found
145
-
146
- Suggestions:
147
- - uc-auth-004: Did you mean uc-auth-003?
148
- - feature-billing: Create plans/features/billing/README.md
149
- ```
150
-
151
- ## Tools Used
152
-
153
- | Tool | Purpose |
154
- |------|---------|
155
- | `Bash` | Run graph.py script |
156
- | `Read` | Read docs-graph.json, docs-graph.md |
157
- | `Glob` | Find plan files |
158
-
159
- ## Integration
160
-
161
- | Skill | Relationship |
162
- |-------|--------------|
163
- | `/debrief` | Creates use cases with wikilinks |
164
- | `/dev-specs` | Creates specs linking to use cases |
165
- | `/dev-scout` | Creates scout.md for features |
166
-
167
- ## Troubleshooting
168
-
169
- **Graph not updating:**
170
- - Check hook is in `.claude/settings.local.json`
171
- - Verify `jq` is installed
172
- - Run `/utils/docs-graph --regenerate` to force update
173
-
174
- **Broken links:**
175
- - Run `/utils/docs-graph --check` to find issues
176
- - Update wikilinks to match node IDs
177
- - Node IDs are lowercase, no slug (e.g., `uc-auth-001` not `UC-AUTH-001-login`)