yolo/agent-skills
3
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: rename tracker common
ci / nix (push) Successful in 8s
Details
ci / lint (push) Successful in 11s
Details

Browse Source
This commit is contained in:
Miguel Palhas
2026-08-20 15:40:17 +01:00
parent 2f092f9ee0
commit 04baf8242a
8 changed files with 46 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/nightshift/SKILL.md
+3 -3
View File
@@ -15,7 +15,7 @@ For work measured in hours, not minutes, with nobody watching. You are the **arc
Use when: a large feature or whole subsystem, an overnight run, "keep going until X works".
Don't use when: the task is one or two files (`/yolo`), or needs a PR review loop (`/work`, `/land`).
**First:** read `linear-common/COMMON.md` (sibling skill, same skills root) for tracker config and worktree setup.
**First:** read `tracker-common/COMMON.md` (sibling skill, same skills root) for tracker config and worktree setup.
## 1. Resolve the input
@@ -111,7 +111,7 @@ What actually works, learned the hard way:
- **Model choice**: strongest model for design-heavy or feel-critical work; a cheaper one is fine for mechanical, well-specified changes.
- Instruct them to **commit their own work locally** when it's coherent, so a killed agent loses less — and explicitly **not to push**. A dozen subagent pushes is a dozen CI runs on half-finished work.
- **Tell them not to run the full suite.** Scoped checks on the files they own, nothing more. Five agents each running every test is five copies of the same work and enough memory pressure to kill the run. You run the full suite once, at push time, through `gate.sh`.
- **Cap the fan-out at 3 concurrent subagents, 2 if their tasks compile or test.** More agents is not more throughput on a box this size — it is swap. `<skills-root>/linear-common/scripts/gate.sh --status` shows how much of the machine other sessions are already using; dispatch fewer when it is contended, and remember other `/yolo` and `/nightshift` runs are competing for the same RAM.
- **Cap the fan-out at 3 concurrent subagents, 2 if their tasks compile or test.** More agents is not more throughput on a box this size — it is swap. `<skills-root>/tracker-common/scripts/gate.sh --status` shows how much of the machine other sessions are already using; dispatch fewer when it is contended, and remember other `/yolo` and `/nightshift` runs are competing for the same RAM.
## 6. Reviewing what lands
@@ -139,7 +139,7 @@ This is what makes an overnight run reviewable by a human who slept through it.
- All work goes on **one branch** in the worktree. Subtasks commit to it **locally**.
- **Push is a deliberate act, not a milestone habit.** Every push runs CI, and a night of milestone pushes is a night of CI runs on work that was half-finished at the time — noisy, expensive, and it trains the user to ignore the build.
- **Push when:** the run finishes, you park on a limit, or the user asks. That's it.
- **Before each of those pushes**, run the full suite once through the gate: `<skills-root>/linear-common/scripts/gate.sh -- <buildCommand>`. Exit 75 means the machine was busy and it never ran — push and say so plainly in the PR body under what is unverified. Exit 137 is the memory cap, not a failing test.
- **Before each of those pushes**, run the full suite once through the gate: `<skills-root>/tracker-common/scripts/gate.sh -- <buildCommand>`. Exit 75 means the machine was busy and it never ran — push and say so plainly in the PR body under what is unverified. Exit 137 is the memory cap, not a failing test.
- **Then open the PR** describing what landed, what is unverified, what you decided and why, and what needs a human. The build log (§7) is most of that text already.
Forge-agnostic: