@groupby/ai-dev 0.3.0 → 0.4.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/README.md
CHANGED
|
@@ -18,7 +18,7 @@ Or install as a dev dependency:
|
|
|
18
18
|
npm install --save-dev @groupby/ai-dev
|
|
19
19
|
```
|
|
20
20
|
|
|
21
|
-
> Requires Node.js >=
|
|
21
|
+
> Requires Node.js >= 20
|
|
22
22
|
|
|
23
23
|
## Usage
|
|
24
24
|
|
|
@@ -62,6 +62,11 @@ When installing a team's skills, you will be prompted to optionally include skil
|
|
|
62
62
|
| `--force` | Overwrite existing files without prompting |
|
|
63
63
|
| `--skip-existing` | Skip files that already exist |
|
|
64
64
|
|
|
65
|
+
`--ai-dir` is resolved relative to `--target` and is intentionally flexible.
|
|
66
|
+
Parent-directory segments such as `../shared-ai` are supported so teams can keep
|
|
67
|
+
AI docs in a workspace-level or shared location while client stubs stay in the
|
|
68
|
+
target project. Use `--dry-run` first when trying a new install layout.
|
|
69
|
+
|
|
65
70
|
## How it works
|
|
66
71
|
|
|
67
72
|
1. **Discovery** — The CLI scans bundled `skills/` and `teams/` directories for `SKILL.md` files and reads their YAML frontmatter (name, description, etc.).
|
|
@@ -84,7 +89,7 @@ When installing a team's skills, you will be prompted to optionally include skil
|
|
|
84
89
|
# Install dependencies
|
|
85
90
|
npm install
|
|
86
91
|
|
|
87
|
-
# Build (also copies skills
|
|
92
|
+
# Build (also copies skills/, teams/, and toolsets/ from the repo root)
|
|
88
93
|
npm run build
|
|
89
94
|
|
|
90
95
|
# Output is in dist/
|
package/package.json
CHANGED
|
@@ -0,0 +1,76 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: sync-components
|
|
3
|
+
description: Sync a multi-repository component workspace by cloning repositories listed in components.txt with minimal inspection. Use when asked to sync up, clone, or refresh project components.
|
|
4
|
+
license: MIT
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Sync Components
|
|
8
|
+
|
|
9
|
+
Use this skill when the user asks to sync up a project's component repositories.
|
|
10
|
+
|
|
11
|
+
## Goal
|
|
12
|
+
|
|
13
|
+
Populate `components/` from the entries in `components.txt` using `git clone`, and leave each synced component on the `main` branch.
|
|
14
|
+
|
|
15
|
+
Keep this workflow lightweight. Do not inspect component source trees, run builds, run tests, scan every repository, or perform broad Git status checks unless the user explicitly asks.
|
|
16
|
+
|
|
17
|
+
Do not create a shell script, temporary script, generated helper, Makefile target, or wrapper command for this workflow. Running generated scripts often triggers extra approval prompts. Use direct shell commands only.
|
|
18
|
+
|
|
19
|
+
## Source Of Truth
|
|
20
|
+
|
|
21
|
+
Read `components.txt` from the framework or workspace checkout.
|
|
22
|
+
|
|
23
|
+
Each non-empty, non-comment line is either:
|
|
24
|
+
|
|
25
|
+
- A full Git remote URL, used as-is.
|
|
26
|
+
- A repository name. If the file uses bare repository names, infer the Git remote from the project instructions or ask the user for the organization/remote prefix before cloning.
|
|
27
|
+
|
|
28
|
+
The local checkout path for each entry is:
|
|
29
|
+
|
|
30
|
+
```text
|
|
31
|
+
components/<repo-name>
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
Derive `<repo-name>` from the entry basename and remove a trailing `.git`.
|
|
35
|
+
|
|
36
|
+
## Workflow
|
|
37
|
+
|
|
38
|
+
1. Confirm the current directory is the framework checkout.
|
|
39
|
+
2. Create `components/` if it does not exist.
|
|
40
|
+
3. Read `components.txt`.
|
|
41
|
+
4. For each component entry:
|
|
42
|
+
- If `components/<repo-name>` does not exist, run:
|
|
43
|
+
|
|
44
|
+
```bash
|
|
45
|
+
git clone <remote> components/<repo-name>
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
- If the directory already exists, keep it and report `exists`.
|
|
49
|
+
- After clone or exists, run:
|
|
50
|
+
|
|
51
|
+
```bash
|
|
52
|
+
git -C components/<repo-name> checkout main
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
- If `main` is not available locally, fetch only the main branch and try again:
|
|
56
|
+
|
|
57
|
+
```bash
|
|
58
|
+
git -C components/<repo-name> fetch origin main
|
|
59
|
+
git -C components/<repo-name> checkout main
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
5. Report only cloned, existing, checked-out-main, skipped, and failed component names.
|
|
63
|
+
|
|
64
|
+
Prefer issuing the `git clone` commands directly from the terminal. It is acceptable to run them one at a time. Do not generate a loop script or ask the user to run a script.
|
|
65
|
+
|
|
66
|
+
## Constraints
|
|
67
|
+
|
|
68
|
+
- Use direct `git clone` commands for this workflow.
|
|
69
|
+
- Do not create, modify, chmod, or execute any sync script.
|
|
70
|
+
- Do not use heredocs, shell redirection, or generated files to automate cloning.
|
|
71
|
+
- Do not delete, reset, clean, or force checkout any component repository.
|
|
72
|
+
- Do not pull existing repositories unless the user asks to update already-cloned components.
|
|
73
|
+
- Do not fetch existing repositories except `git fetch origin main` when needed to make `main` available for checkout.
|
|
74
|
+
- Do not open or validate component-local instruction files during this sync workflow.
|
|
75
|
+
- Do not run dependency installation, tests, formatters, linters, or builds.
|
|
76
|
+
- Keep all cloned repositories directly under `components/`.
|