deepflow 0.1.79 → 0.1.81
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/README.md +14 -3
- package/bin/install.js +3 -2
- package/package.json +4 -1
- package/src/commands/df/auto-cycle.md +17 -2
- package/src/commands/df/execute.md +39 -9
- package/src/commands/df/plan.md +49 -0
- package/src/commands/df/verify.md +433 -3
- package/src/skills/browse-fetch/SKILL.md +416 -0
- package/src/skills/browse-verify/SKILL.md +264 -0
- package/templates/config-template.yaml +14 -0
- package/src/skills/context-hub/SKILL.md +0 -87
|
@@ -1,87 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: context-hub
|
|
3
|
-
description: Fetches curated API docs for external libraries before coding. Use when implementing code that uses external APIs/SDKs (Stripe, OpenAI, MongoDB, etc.) to avoid hallucinating APIs and reduce token usage.
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Context Hub
|
|
7
|
-
|
|
8
|
-
Fetch curated, versioned docs for external libraries instead of guessing APIs.
|
|
9
|
-
|
|
10
|
-
## When to Use
|
|
11
|
-
|
|
12
|
-
Before writing code that calls an external API or SDK:
|
|
13
|
-
- New library integration (e.g., Stripe payments, AWS S3)
|
|
14
|
-
- Unfamiliar API version or method
|
|
15
|
-
- Complex API with many options (e.g., MongoDB aggregation)
|
|
16
|
-
|
|
17
|
-
**Skip when:** Working with internal code (use LSP instead) or well-known stdlib APIs.
|
|
18
|
-
|
|
19
|
-
## Prerequisites
|
|
20
|
-
|
|
21
|
-
Requires `chub` CLI: `npm install -g @aisuite/chub`
|
|
22
|
-
|
|
23
|
-
If `chub` is not installed, tell the user and skip — don't block implementation.
|
|
24
|
-
|
|
25
|
-
## Workflow
|
|
26
|
-
|
|
27
|
-
### 1. Search for docs
|
|
28
|
-
|
|
29
|
-
```bash
|
|
30
|
-
chub search "<library or API>" --json
|
|
31
|
-
```
|
|
32
|
-
|
|
33
|
-
Example:
|
|
34
|
-
```bash
|
|
35
|
-
chub search "stripe payments" --json
|
|
36
|
-
chub search "mongodb aggregation" --json
|
|
37
|
-
```
|
|
38
|
-
|
|
39
|
-
### 2. Fetch relevant docs
|
|
40
|
-
|
|
41
|
-
```bash
|
|
42
|
-
chub get <id> --lang <py|js|ts>
|
|
43
|
-
```
|
|
44
|
-
|
|
45
|
-
Use `--lang` matching the project language. Use `--full` only if the summary lacks what you need.
|
|
46
|
-
|
|
47
|
-
### 3. Write code using fetched docs
|
|
48
|
-
|
|
49
|
-
Use the retrieved documentation as ground truth for API signatures, parameter names, and patterns.
|
|
50
|
-
|
|
51
|
-
### 4. Annotate discoveries
|
|
52
|
-
|
|
53
|
-
When you find something the docs missed or got wrong:
|
|
54
|
-
|
|
55
|
-
```bash
|
|
56
|
-
chub annotate <id> "Note: method X requires param Y since v2.0"
|
|
57
|
-
```
|
|
58
|
-
|
|
59
|
-
This persists locally and appears on future `chub get` calls — the agent learns across sessions.
|
|
60
|
-
|
|
61
|
-
### 5. Rate docs (optional)
|
|
62
|
-
|
|
63
|
-
```bash
|
|
64
|
-
chub feedback <id> up --label accurate
|
|
65
|
-
chub feedback <id> down --label outdated
|
|
66
|
-
```
|
|
67
|
-
|
|
68
|
-
Labels: `accurate`, `outdated`, `incomplete`, `wrong-version`, `helpful`
|
|
69
|
-
|
|
70
|
-
## Integration with LSP
|
|
71
|
-
|
|
72
|
-
| Need | Tool |
|
|
73
|
-
|------|------|
|
|
74
|
-
| Internal code navigation | LSP (`goToDefinition`, `findReferences`) |
|
|
75
|
-
| External API signatures | Context Hub (`chub get`) |
|
|
76
|
-
| Symbol search in project | LSP (`workspaceSymbol`) |
|
|
77
|
-
| Library usage patterns | Context Hub (`chub search`) |
|
|
78
|
-
|
|
79
|
-
**Combined approach:** Use LSP to understand how the project currently uses a library, then use Context Hub to verify correct API usage and discover better patterns.
|
|
80
|
-
|
|
81
|
-
## Rules
|
|
82
|
-
|
|
83
|
-
- Always search before implementing external API calls
|
|
84
|
-
- Trust chub docs over training data for API specifics
|
|
85
|
-
- Annotate gaps so future sessions benefit
|
|
86
|
-
- Don't block on chub failures — fall back to best knowledge
|
|
87
|
-
- Prefer `--json` flag for programmatic parsing in automated workflows
|