@gallopsystems/agent-skills 1.31.0 → 1.31.2
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/plugins/gallop-ui/skills/gallop-ui/SKILL.md +2 -2
- package/plugins/gallop-ui/skills/gallop-ui/changing-the-layer.md +3 -3
- package/plugins/gallop-ui/skills/gallop-ui/finding-a-component.md +2 -2
- package/plugins/gallop-ui/skills/gallop-ui/pulling-updates.md +2 -2
- package/plugins/nitro-testing/skills/nitro-testing/ci-setup.md +18 -23
package/package.json
CHANGED
|
@@ -27,8 +27,8 @@ colour tokens.
|
|
|
27
27
|
| `CLAUDE.md` | The layer's rules for people and agents who change it. |
|
|
28
28
|
| `README.md` | Adding the layer, taking versions, customizing (`pt`, `gallopUi`), restyling states. |
|
|
29
29
|
| `TOKENS.md`, `FORMATTERS.md` | The colour-token contract; `formatDate`, `formatCurrency`… and time zones. |
|
|
30
|
-
| `CHANGELOG.md`, `migrations/<version>/`, `docs/
|
|
31
|
-
| `docs/decisions.md` | Settled API names and
|
|
30
|
+
| `CHANGELOG.md`, `migrations/<version>/`, `docs/upgrading.md` | What changed, how to take a release, and the codemod tables. |
|
|
31
|
+
| `docs/decisions.md` | Settled API names and the reasons for them. Read before proposing a rename. |
|
|
32
32
|
| `docs/playground.md` | `/_ui` and `yarn ui:impact`. |
|
|
33
33
|
|
|
34
34
|
`yarn ui:version` prints the app's layer version.
|
|
@@ -5,7 +5,7 @@ Fixes and features for the layer are made **in the gallop-ui repo** (`gallop-sys
|
|
|
5
5
|
app, so the bar is higher than for app code: backward compatible, documented, tested, and checked in every app.
|
|
6
6
|
|
|
7
7
|
The layer's `CLAUDE.md` is the authority on its rules. Read it, `docs/decisions.md` (settled names) and
|
|
8
|
-
`docs/
|
|
8
|
+
`docs/roadmap.md` (what's planned and open) before you start.
|
|
9
9
|
|
|
10
10
|
## 1. Worktree
|
|
11
11
|
|
|
@@ -86,8 +86,8 @@ yarn tokens:check # if you touched tokens
|
|
|
86
86
|
the `Co-Authored-By` trailer you were given.
|
|
87
87
|
- The PR body: what changed and why, the apps you checked with `impact.mjs` and what changed in each, and any naming
|
|
88
88
|
call the owner still has to make. End it with the Claude Code line you were given.
|
|
89
|
-
- Record a decision
|
|
90
|
-
|
|
89
|
+
- Record a settled decision, with its reason, in `docs/decisions.md`. Add planned or open work to `docs/roadmap.md`,
|
|
90
|
+
and remove it there when it ships.
|
|
91
91
|
- **Layer PRs are squash-merged**, with the PR title as the Conventional Commit. A merge commit hides the change
|
|
92
92
|
from release-please.
|
|
93
93
|
- Merge only when checks are green **and** `gh pr view <n> --json mergeStateStatus` says `CLEAN`, and only if you
|
|
@@ -88,5 +88,5 @@ The owner decides names and whether the layer grows. Bring a short proposal, not
|
|
|
88
88
|
`docs/decisions.md` so you don't reopen a settled name.
|
|
89
89
|
- **What it replaces**, and whether adopting it is a scripted rewrite.
|
|
90
90
|
|
|
91
|
-
|
|
92
|
-
|
|
91
|
+
In the gallop-ui repo, `docs/roadmap.md` ("Later") lists ideas not built yet, and `docs/decisions.md` ("Considered
|
|
92
|
+
and not built") lists what was declined and why. Check both first. A new idea goes in `docs/roadmap.md`.
|
|
@@ -36,12 +36,12 @@ yarn ui:pull v<X.Y.Z> # git subtree pull --squash, committed as "chore(ga
|
|
|
36
36
|
|
|
37
37
|
```sh
|
|
38
38
|
sed -n '/^## \[<X.Y.Z>\]/,/^## \[<current>\]/p' layers/gallop-ui/CHANGELOG.md
|
|
39
|
-
ls layers/gallop-ui/migrations
|
|
39
|
+
ls layers/gallop-ui/migrations/; cat layers/gallop-ui/docs/upgrading.md
|
|
40
40
|
```
|
|
41
41
|
|
|
42
42
|
For each entry, decide: does this app call it (`git grep -n "<Component\|propName" -- app tests`), and does the call
|
|
43
43
|
site need to change? Read the affected components' `.md` "Migrating" sections. A release that crosses a major
|
|
44
|
-
version has a `docs/
|
|
44
|
+
version has a `migrations/<version>/` folder; `docs/upgrading.md` explains how to apply it. Jumping several releases is
|
|
45
45
|
fine as long as you read every entry in between. The kit only knows the versions it has tables for, so check the
|
|
46
46
|
migration doc for how far back it reaches.
|
|
47
47
|
|
|
@@ -179,37 +179,32 @@ Configure branch protection rules in GitHub:
|
|
|
179
179
|
- `test`
|
|
180
180
|
- `typecheck`
|
|
181
181
|
|
|
182
|
-
##
|
|
182
|
+
## Running the CI tests locally
|
|
183
183
|
|
|
184
|
-
|
|
184
|
+
Run the same tests against a disposable **native** Postgres (Postgres.app's binaries), not Docker. Don't start Docker
|
|
185
|
+
(`docker run`, `docker compose`, `open -a Docker`, testcontainers, `act`) unless the user asks for it. Use your own
|
|
186
|
+
port, never 5432, 5433 or 3306, so a test run can never reach a real local database:
|
|
185
187
|
|
|
186
188
|
```bash
|
|
187
|
-
|
|
188
|
-
|
|
189
|
+
PG=/Applications/Postgres.app/Contents/Versions/latest/bin
|
|
190
|
+
$PG/initdb --locale=en_US.UTF-8 -U postgres -D /tmp/myapp-pg
|
|
191
|
+
$PG/pg_ctl -D /tmp/myapp-pg -l /tmp/myapp-pg.log -o "-p 54329 -c fsync=off -c synchronous_commit=off \
|
|
192
|
+
-c full_page_writes=off" start
|
|
193
|
+
$PG/createdb -h 127.0.0.1 -p 54329 -U postgres myapp-test
|
|
189
194
|
|
|
190
|
-
# Run
|
|
191
|
-
|
|
192
|
-
```
|
|
193
|
-
|
|
194
|
-
Or use Docker directly:
|
|
195
|
-
|
|
196
|
-
```bash
|
|
197
|
-
# Start test database
|
|
198
|
-
docker run -d --name test-db \
|
|
199
|
-
-e POSTGRES_USER=postgres \
|
|
200
|
-
-e POSTGRES_PASSWORD=postgres \
|
|
201
|
-
-e POSTGRES_DB=myapp-test \
|
|
202
|
-
-p 5432:5432 \
|
|
203
|
-
postgres:15
|
|
204
|
-
|
|
205
|
-
# Run tests
|
|
206
|
-
TEST_POSTGRESQL_CONNECTION_STRING=postgresql://postgres:postgres@localhost:5432/myapp-test \
|
|
207
|
-
yarn test
|
|
195
|
+
# Run tests (127.0.0.1, not localhost)
|
|
196
|
+
TEST_POSTGRESQL_CONNECTION_STRING=postgresql://postgres@127.0.0.1:54329/myapp-test yarn test
|
|
208
197
|
|
|
209
198
|
# Cleanup
|
|
210
|
-
|
|
199
|
+
$PG/pg_ctl -D /tmp/myapp-pg stop && rm -rf /tmp/myapp-pg
|
|
211
200
|
```
|
|
212
201
|
|
|
202
|
+
Before running, check that the test URL is set and doesn't point at 5432. An unset test URL can fall back to the
|
|
203
|
+
developer's real database.
|
|
204
|
+
|
|
205
|
+
If the user wants the workflow itself replayed, [act](https://github.com/nektos/act) runs it, but act needs Docker,
|
|
206
|
+
so only with their go-ahead.
|
|
207
|
+
|
|
213
208
|
## Secrets and Environment Variables
|
|
214
209
|
|
|
215
210
|
For production-like test databases or external services:
|