@infinitedusky/indusk-mcp 0.2.0 → 0.3.0
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/skills/toolbelt.md +80 -0
package/package.json
CHANGED
|
@@ -0,0 +1,80 @@
|
|
|
1
|
+
# InDusk Toolbelt
|
|
2
|
+
|
|
3
|
+
You have MCP tools from two servers: **indusk** (dev system) and **codegraphcontext** (code graph). This skill tells you when to use them.
|
|
4
|
+
|
|
5
|
+
## Session Start
|
|
6
|
+
|
|
7
|
+
When a new session begins:
|
|
8
|
+
|
|
9
|
+
1. Call `check_health` — verify FalkorDB and CGC are running. If unhealthy, tell the user what's down and how to fix it before proceeding.
|
|
10
|
+
2. Call `list_plans` — understand what plans exist, their stages, and what's in progress.
|
|
11
|
+
3. Call `get_context` — read the project's CLAUDE.md to understand architecture, conventions, and current state.
|
|
12
|
+
|
|
13
|
+
## Before Modifying Code
|
|
14
|
+
|
|
15
|
+
Before touching any file:
|
|
16
|
+
|
|
17
|
+
1. Call `get_plan_status` for the active plan — know which phase you're in and what items remain.
|
|
18
|
+
2. Use CGC's `analyze_code_relationships` on the files you're about to change — understand dependencies and blast radius.
|
|
19
|
+
3. If the blast radius is large (many downstream consumers), flag it to the user before proceeding.
|
|
20
|
+
|
|
21
|
+
## During Work
|
|
22
|
+
|
|
23
|
+
While executing impl items:
|
|
24
|
+
|
|
25
|
+
- After completing verification items, call `quality_check` to confirm Biome passes.
|
|
26
|
+
- After completing context items, call `get_context` to verify CLAUDE.md was updated correctly.
|
|
27
|
+
- After completing document items, call `list_docs` to verify the doc page exists.
|
|
28
|
+
|
|
29
|
+
## Advancing Phases
|
|
30
|
+
|
|
31
|
+
When you think a phase is complete:
|
|
32
|
+
|
|
33
|
+
1. Call `advance_plan` — it will tell you if anything is missing across all four gates (implementation, verification, context, document).
|
|
34
|
+
2. If blocked, work through the missing items before trying again.
|
|
35
|
+
3. Never manually mark a phase complete without calling `advance_plan` first.
|
|
36
|
+
|
|
37
|
+
## After a Retrospective
|
|
38
|
+
|
|
39
|
+
1. Call `check_docs_coverage` — flag any completed plans missing decision pages.
|
|
40
|
+
2. Call `get_quality_config` — review if new Biome rules should be added based on lessons learned.
|
|
41
|
+
3. If a new rule is needed, call `suggest_rule` with a description of the mistake to find matching Biome rules.
|
|
42
|
+
|
|
43
|
+
## Skill and System Management
|
|
44
|
+
|
|
45
|
+
- Call `get_skill_versions` to check if installed skills are current or outdated.
|
|
46
|
+
- Call `get_system_version` to verify the installed package version.
|
|
47
|
+
|
|
48
|
+
## Code Graph (CGC Tools)
|
|
49
|
+
|
|
50
|
+
These come from the codegraphcontext MCP server:
|
|
51
|
+
|
|
52
|
+
| When | Tool |
|
|
53
|
+
|------|------|
|
|
54
|
+
| Search for code by name | `find_code` |
|
|
55
|
+
| Understand what depends on a file | `analyze_code_relationships` |
|
|
56
|
+
| Find complex functions to refactor | `find_most_complex_functions` |
|
|
57
|
+
| Check for dead code | `find_dead_code` |
|
|
58
|
+
| Scope a plan during research | `analyze_code_relationships` on the target area |
|
|
59
|
+
| Custom graph queries | `execute_cypher_query` |
|
|
60
|
+
|
|
61
|
+
## Tool Reference
|
|
62
|
+
|
|
63
|
+
### indusk (14 tools)
|
|
64
|
+
|
|
65
|
+
| Tool | When to use |
|
|
66
|
+
|------|-------------|
|
|
67
|
+
| `list_plans` | Session start, orientation |
|
|
68
|
+
| `get_plan_status` | Before working on a plan, checking progress |
|
|
69
|
+
| `advance_plan` | End of every phase — validates all gates |
|
|
70
|
+
| `order_plans` | Understanding plan dependencies |
|
|
71
|
+
| `get_context` | Session start, after context updates |
|
|
72
|
+
| `update_context` | Updating CLAUDE.md sections programmatically |
|
|
73
|
+
| `get_quality_config` | Reviewing Biome rules, after retros |
|
|
74
|
+
| `suggest_rule` | Finding Biome rules for new patterns |
|
|
75
|
+
| `quality_check` | After verification items, before advancing |
|
|
76
|
+
| `list_docs` | After document items, checking coverage |
|
|
77
|
+
| `check_docs_coverage` | After retros, finding doc gaps |
|
|
78
|
+
| `get_system_version` | Debugging, version checks |
|
|
79
|
+
| `get_skill_versions` | Checking for outdated skills |
|
|
80
|
+
| `check_health` | Session start, debugging connectivity |
|