Skip to content

Commit 1f03741

Browse files
committed
docs(skills): correct the nix/tools runtime and format-commit wording
The profiling skill said the tools under nix/tools run on node; all three are built with bunCli or bunNodeModules and run under Bun, so `node --cpu-prof` would profile nothing. The commit skill's `chore: format` line now says when a scope is required, since an adapter-only format commit needs one.
1 parent ec1b0e0 commit 1f03741

2 files changed

Lines changed: 6 additions & 5 deletions

File tree

‎.agents/skills/commit/SKILL.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ The subject names the artifact or behavior changed and reads sensibly alone in a
3838

3939
The `commit-msg` hook runs `scripts/validate-commit-scope.nu`: when staged paths live under `rust/adapters/<agent>/`, the scope must be that agent (`fix(kimi)`), one of the cross-cutting scopes, or — for a change spanning several agents — a workspace scope. `rust/adapters/common/` derives `adapter`, not `common`. Read the script for the current lists; no other part of the tree derives a scope.
4040

41-
Formatter-only changes are `chore: format` or `chore(<scope>): format`. Messages are US English.
41+
Formatter-only changes are `chore: format`, or `chore(<scope>): format` when the scope rule above applies. Messages are US English.
4242

4343
## Push (push=true)
4444

‎.agents/skills/profile/SKILL.md‎

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,11 @@ profile of it covers launcher startup, not the work the binary does:
2828
LOG_LEVEL=0 node --cpu-prof --cpu-prof-dir /tmp/ccusage-profiles apps/ccusage/src/cli.js daily --offline --json
2929
```
3030

31-
The same applies to the TypeScript tools under `nix/tools/`, which run on
32-
`node`. Scripts in `apps/ccusage/scripts/` do not: they carry `nix shell`
33-
shebangs that pick nushell, babashka, or bun, so time the script itself and
34-
profile with that runtime's own tooling rather than `NODE_OPTIONS`.
31+
Nothing else here runs on `node`. The tools under `nix/tools/` are built with
32+
`bunCli`/`bunNodeModules` and run under Bun; scripts in `apps/ccusage/scripts/`
33+
carry `nix shell` shebangs that pick nushell, babashka, or bun. Time those
34+
scripts directly and profile with their own runtime's tooling rather than
35+
`NODE_OPTIONS`.
3536

3637
Read `.cpuprofile` output bottom-up by self time in Chrome DevTools or the VS
3738
Code profiler, and map hot frames back to source with `rg`. Point

0 commit comments

Comments
 (0)