si-overnight 0.0.0-stage → 0.1.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 +269 -2
- package/README.tr.md +247 -0
- package/bin/si-overnight.mjs +48 -0
- package/docs/assets/overnight-workflow.gif +0 -0
- package/lib/install.mjs +151 -0
- package/package.json +34 -4
- package/skills/si-overnight/SKILL.md +179 -0
- package/skills/si-overnight/references/platforms.md +56 -0
- package/skills/si-overnight/references/run-template.md +70 -0
package/README.md
CHANGED
|
@@ -1,3 +1,270 @@
|
|
|
1
|
-
#
|
|
1
|
+
# si-overnight
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
**English** · [Türkçe](https://github.com/siguelabs/si/blob/main/README.tr.md)
|
|
4
|
+
|
|
5
|
+
Give your coding agent a clear plan before you sleep. `si-overnight` helps it
|
|
6
|
+
finish agreed work, test the changes, save checkpoints, and leave a morning report.
|
|
7
|
+
|
|
8
|
+
It is a portable [Agent Skill](https://agentskills.io/), with installers for
|
|
9
|
+
Codex, Claude Code, Google Antigravity, and pi. The skill supplies the workflow;
|
|
10
|
+
your agent host supplies the tools, permissions, and execution time.
|
|
11
|
+
|
|
12
|
+

|
|
13
|
+
|
|
14
|
+
*Illustrative workflow diagram, not a recording of an agent session. Parallel
|
|
15
|
+
workers are optional and require host support.*
|
|
16
|
+
|
|
17
|
+
[Quick start](#quick-start) · [How it works](#how-it-works) ·
|
|
18
|
+
[Hosts and paths](#hosts-and-installation-paths) · [Resume](#resume-a-run) ·
|
|
19
|
+
[Development](#development-and-contributing)
|
|
20
|
+
|
|
21
|
+
## Quick start
|
|
22
|
+
|
|
23
|
+
Use the source checkout today. The Node.js installer requires **Node.js 20+**,
|
|
24
|
+
has no package dependencies, and does not require Python.
|
|
25
|
+
|
|
26
|
+
```bash
|
|
27
|
+
git clone https://github.com/siguelabs/si.git
|
|
28
|
+
cd si
|
|
29
|
+
node bin/si-overnight.mjs --platform codex --project /absolute/path/to/project
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
If you already have this repository, run the `node bin/si-overnight.mjs ...`
|
|
33
|
+
command from its root. Choose `claude`, `antigravity`, or `pi` for another host,
|
|
34
|
+
or `all` for every supported host. The target project directory must already
|
|
35
|
+
exist. Open that project in your host and invoke the skill with its command below.
|
|
36
|
+
|
|
37
|
+
For example, in Codex:
|
|
38
|
+
|
|
39
|
+
```text
|
|
40
|
+
$si-overnight
|
|
41
|
+
Tonight, fix the checkout bugs in issues #12 and #18.
|
|
42
|
+
Ask me for the remaining decisions before I leave.
|
|
43
|
+
Work for at most six hours from the start of this run.
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
Replace the tasks and deadline with your own. The agent inspects the project and
|
|
47
|
+
collects the missing decisions before implementation starts. A bare invocation
|
|
48
|
+
starts intake; it does not authorize an unspecified night of changes.
|
|
49
|
+
|
|
50
|
+
### npm installation
|
|
51
|
+
|
|
52
|
+
Install the latest published release:
|
|
53
|
+
|
|
54
|
+
```bash
|
|
55
|
+
npx --yes si-overnight --platform all --project /absolute/path/to/project
|
|
56
|
+
npx --yes si-overnight --platform codex --scope user
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
To try the current package without a registry release, run from this repository:
|
|
60
|
+
|
|
61
|
+
```bash
|
|
62
|
+
npm pack --ignore-scripts
|
|
63
|
+
npm exec --yes --package ./si-overnight-0.1.1.tgz -- si-overnight --platform codex --project /absolute/path/to/project
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
Installing the npm package, including globally, only makes the installer command
|
|
67
|
+
available. It does not install skills automatically or launch an agent. Run the
|
|
68
|
+
installer explicitly, then invoke the skill in your host.
|
|
69
|
+
|
|
70
|
+
## How it works
|
|
71
|
+
|
|
72
|
+
### 1. Agree on tonight's work
|
|
73
|
+
|
|
74
|
+
The agent reads project instructions, existing changes, build commands, and test
|
|
75
|
+
setup. For **each new night**, it asks you to choose a mode unless you have already
|
|
76
|
+
chosen one for that run:
|
|
77
|
+
|
|
78
|
+
| Mode | After the primary tasks |
|
|
79
|
+
| --- | --- |
|
|
80
|
+
| **Queue** | Finish your agreed backup tasks, then stop. |
|
|
81
|
+
| **Discover** | Find and implement useful improvements inside the areas and categories you agreed on. |
|
|
82
|
+
|
|
83
|
+
Last night's choice is not a permanent preference. Resuming an existing run keeps
|
|
84
|
+
that run's mode and scope.
|
|
85
|
+
|
|
86
|
+
Before you leave, the agent batches the consequential questions:
|
|
87
|
+
|
|
88
|
+
- What outcomes matter most, and what proves they are done?
|
|
89
|
+
- Which backup tasks or discovery areas are allowed? Are dependency changes or broad refactors included?
|
|
90
|
+
- Which paths, APIs, behavior, data, or design decisions must remain unchanged?
|
|
91
|
+
- When should work stop, with a date and timezone or duration? Is there a known spend or token cap?
|
|
92
|
+
- Which tests and services are available? Are access or permission prompts likely?
|
|
93
|
+
- Should delivery be local edits and a report, or are commits, a push/PR, deployment, or other external actions authorized?
|
|
94
|
+
|
|
95
|
+
It reuses answers already in the conversation and checks likely blockers while
|
|
96
|
+
you can still respond. Your answers authorize the agreed work; no extra start
|
|
97
|
+
confirmation is needed. Unanswered questions remain unanswered when you go offline.
|
|
98
|
+
|
|
99
|
+
### 2. Implement, test, review, checkpoint
|
|
100
|
+
|
|
101
|
+
The agent saves the run contract and repeats this loop while useful authorized
|
|
102
|
+
work and time remain:
|
|
103
|
+
|
|
104
|
+
1. Read the checkpoint; check scope, time, and any observable budget.
|
|
105
|
+
2. Pick the highest-priority unblocked task and implement a bounded change.
|
|
106
|
+
3. Run focused tests, fix demonstrated regressions, and run required broader checks.
|
|
107
|
+
4. Review the diff for correctness, scope, and unrelated changes.
|
|
108
|
+
5. Save the evidence, work in progress, and next action before continuing.
|
|
109
|
+
|
|
110
|
+
Existing user edits are preserved. A blocked task is recorded while independent
|
|
111
|
+
work continues. Repeated attempts without new evidence are bounded. Passing tests
|
|
112
|
+
are not rerun merely to consume tokens, and unavailable checks are not reported
|
|
113
|
+
as passing.
|
|
114
|
+
|
|
115
|
+
**Optional subagents:** on hosts that support them, the main agent can coordinate
|
|
116
|
+
independent tasks and assign nonoverlapping file ownership. It may also delegate
|
|
117
|
+
tests or a review, then verify the results. These are task assignments chosen for
|
|
118
|
+
the run, not a built-in team of always-on agents. Every worker shares the same
|
|
119
|
+
scope, deadline, and permissions.
|
|
120
|
+
|
|
121
|
+
### 3. Stop with a useful handoff
|
|
122
|
+
|
|
123
|
+
Work stops when the Queue is complete, scoped Discover work has no worthwhile
|
|
124
|
+
candidate left, the deadline or an observable budget/provider limit is reached,
|
|
125
|
+
all remaining work is blocked, you request a stop, or the host ends execution.
|
|
126
|
+
|
|
127
|
+
The agent writes these files in the target project, using your language:
|
|
128
|
+
|
|
129
|
+
| File | Contents |
|
|
130
|
+
| --- | --- |
|
|
131
|
+
| `.si-overnight/<run-id>/run.md` | Scope, answers, baseline, task queue, latest checkpoint, and verification evidence. |
|
|
132
|
+
| `.si-overnight/<run-id>/report.md` | Completed outcomes, changed files, test results, unfinished work, stop reason, and a resume prompt. |
|
|
133
|
+
|
|
134
|
+
Run files stay local and out of staging unless you ask to version them. Checkpoints
|
|
135
|
+
are saved after completed tasks, material failed attempts, and permission blockers,
|
|
136
|
+
and before risky operations or context handoffs. See the
|
|
137
|
+
[checkpoint template](skills/si-overnight/references/run-template.md).
|
|
138
|
+
|
|
139
|
+
## Hosts and installation paths
|
|
140
|
+
|
|
141
|
+
`--scope project` installs below the selected project; `--scope user` installs
|
|
142
|
+
below your home directory. Each destination contains `SKILL.md` and its references.
|
|
143
|
+
|
|
144
|
+
| Host / `--platform` | Project path | User path | Invocation |
|
|
145
|
+
| --- | --- | --- | --- |
|
|
146
|
+
| Codex / `codex` | `.agents/skills/si-overnight/` | `~/.agents/skills/si-overnight/` | `$si-overnight` or select via `/skills` |
|
|
147
|
+
| Claude Code / `claude` | `.claude/skills/si-overnight/` | `~/.claude/skills/si-overnight/` | `/si-overnight` |
|
|
148
|
+
| Google Antigravity / `antigravity` | `.agents/skills/si-overnight/` | `~/.gemini/config/skills/si-overnight/` | `/si-overnight` |
|
|
149
|
+
| pi / `pi` | `.pi/skills/si-overnight/` | `~/.pi/agent/skills/si-overnight/` | `/skill:si-overnight` |
|
|
150
|
+
|
|
151
|
+
Codex and Antigravity share a project destination, so `all` installs one copy
|
|
152
|
+
there. For other Agent Skills-compatible hosts, copy `skills/si-overnight/` into
|
|
153
|
+
the host's documented skill directory and use its invocation mechanism. If a host
|
|
154
|
+
can read files but has no native skill support, explicitly ask it to read and
|
|
155
|
+
follow `SKILL.md`; that does not register a slash command.
|
|
156
|
+
|
|
157
|
+
Paths and commands depend on the installed host version. See
|
|
158
|
+
[compatibility notes and official sources](skills/si-overnight/references/platforms.md).
|
|
159
|
+
|
|
160
|
+
### Installer options
|
|
161
|
+
|
|
162
|
+
```bash
|
|
163
|
+
node bin/si-overnight.mjs --platform claude --platform pi --dry-run
|
|
164
|
+
node bin/si-overnight.mjs --platform codex --scope user
|
|
165
|
+
node bin/si-overnight.mjs --help
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
| Option | Behavior |
|
|
169
|
+
| --- | --- |
|
|
170
|
+
| `--platform <name>` | Required. `codex`, `claude`, `antigravity`, `pi`, or `all`; repeatable. |
|
|
171
|
+
| `--scope <scope>` | `project` by default, or `user`. |
|
|
172
|
+
| `--project <path>` | Existing project directory; defaults to the current directory. Used for project scope. |
|
|
173
|
+
| `--dry-run` | Validate and show destinations without writing files. |
|
|
174
|
+
| `--help`, `-h` | Show CLI help. |
|
|
175
|
+
|
|
176
|
+
The installer leaves identical installations untouched and refuses to overwrite
|
|
177
|
+
different content. To update, review and move the existing skill directory, then
|
|
178
|
+
install again. It checks all destinations before writing, rejects symbolic links
|
|
179
|
+
inside the source or destination tree and below the selected installation root,
|
|
180
|
+
and prevents source/destination overlap. The selected project or home root itself
|
|
181
|
+
may be a directory alias. Avoid concurrent changes to installation directories.
|
|
182
|
+
Installation does not change host permissions or start background processes.
|
|
183
|
+
|
|
184
|
+
A **Python 3 alternative** is available from the repository, with the same
|
|
185
|
+
destinations, dry-run behavior, and protection for existing content:
|
|
186
|
+
|
|
187
|
+
```bash
|
|
188
|
+
python3 scripts/install.py --platform all --project /absolute/path/to/project
|
|
189
|
+
python3 scripts/install.py --platform codex --scope user --dry-run
|
|
190
|
+
```
|
|
191
|
+
|
|
192
|
+
## Execution time and budgets
|
|
193
|
+
|
|
194
|
+
The skill cannot keep a computer awake, restart a stopped agent, renew a quota,
|
|
195
|
+
or create new turns after the host stops. Leave the local machine, session, agent,
|
|
196
|
+
and required services available, or use a host that actually executes remotely.
|
|
197
|
+
A sudden termination may leave only the latest checkpoint; a stopped process
|
|
198
|
+
cannot write a new morning report.
|
|
199
|
+
|
|
200
|
+
A token or spend cap can only be monitored when the host exposes reliable usage
|
|
201
|
+
data. Otherwise usage is recorded as unknown. The skill does not promise to
|
|
202
|
+
consume every available token or wait for quota resets.
|
|
203
|
+
|
|
204
|
+
On Codex versions with Goal mode, you can explicitly start `/goal` with the agreed
|
|
205
|
+
overnight plan. Invoking this skill does not create a goal or schedule. Other
|
|
206
|
+
hosts may need a separately configured runner for repeated invocations; this
|
|
207
|
+
package does not include one. Host approval requirements still apply.
|
|
208
|
+
|
|
209
|
+
## Resume a run
|
|
210
|
+
|
|
211
|
+
Invoke the skill in your host and name the saved checkpoint:
|
|
212
|
+
|
|
213
|
+
```text
|
|
214
|
+
Use si-overnight. Resume .si-overnight/<run-id>/run.md.
|
|
215
|
+
Reconcile the checkpoint with the working tree first and keep the agreed scope.
|
|
216
|
+
The new execution window ends at <date, time, timezone>.
|
|
217
|
+
```
|
|
218
|
+
|
|
219
|
+
The agent checks current instructions, the diff, and other actors' edits before
|
|
220
|
+
continuing. If the old deadline has expired, provide a new window. Completed work
|
|
221
|
+
is retained; an interrupted command is not assumed to have succeeded.
|
|
222
|
+
|
|
223
|
+
## Development and contributing
|
|
224
|
+
|
|
225
|
+
The workflow lives in [`skills/si-overnight/SKILL.md`](skills/si-overnight/SKILL.md).
|
|
226
|
+
Its `references/` directory holds host guidance and the checkpoint template.
|
|
227
|
+
`bin/` and `lib/` contain the dependency-free Node installer; `scripts/install.py`
|
|
228
|
+
is the Python alternative. Installer tests live in `tests/`.
|
|
229
|
+
|
|
230
|
+
To regenerate the workflow illustration, run `python3 scripts/render_workflow.py`.
|
|
231
|
+
The generator requires Pillow for development only; neither installer needs it.
|
|
232
|
+
|
|
233
|
+
Keep changes focused, update both READMEs when behavior changes, and include
|
|
234
|
+
verification evidence with your contribution. Run from the repository root:
|
|
235
|
+
|
|
236
|
+
```bash
|
|
237
|
+
npm test
|
|
238
|
+
python3 -m unittest discover -s tests -v
|
|
239
|
+
```
|
|
240
|
+
|
|
241
|
+
CI runs both suites on Node.js 20 and 24 for branch pushes and pull requests.
|
|
242
|
+
The Node.js 24 job also packs the package, installs it offline with an empty npm
|
|
243
|
+
cache, checks the CLI, and compares every installed skill resource byte for byte.
|
|
244
|
+
The tested tarball and SHA-256 digest are retained in the `npm-package` artifact
|
|
245
|
+
for 14 days. No dependency installation or lockfile is needed.
|
|
246
|
+
|
|
247
|
+
### npm releases
|
|
248
|
+
|
|
249
|
+
A stable tag such as `v0.1.1` must match `package.json`. `release.yml` reruns CI,
|
|
250
|
+
verifies the artifact's checksum, and publishes that same tarball with public
|
|
251
|
+
access and provenance. Prerelease tags are rejected. Only the publish job gets
|
|
252
|
+
OIDC permission; it uses Node.js 24 and checks for npm 11.5.1 or newer. Actions
|
|
253
|
+
are pinned to full commit SHAs and lifecycle scripts are disabled.
|
|
254
|
+
|
|
255
|
+
For maintainers, configure npm Trusted Publishing for **siguelabs / si**, workflow
|
|
256
|
+
filename **release.yml**, with no environment, and enable **Allow npm publish**.
|
|
257
|
+
The package record must exist first, and the repository must be public with the
|
|
258
|
+
matching `repository.url`. This workflow requires no `NPM_TOKEN`. Restrict who
|
|
259
|
+
can create release tags through GitHub repository rulesets.
|
|
260
|
+
|
|
261
|
+
If the release is staged, a maintainer must approve it in npm **Staged Packages**
|
|
262
|
+
before users can install it. A successful staging step is not a public release.
|
|
263
|
+
See [npm staged publishing](https://docs.npmjs.com/staged-publishing/),
|
|
264
|
+
[Trusted Publishers](https://docs.npmjs.com/trusted-publishers/), and
|
|
265
|
+
[provenance requirements](https://docs.npmjs.com/generating-provenance-statements/).
|
|
266
|
+
|
|
267
|
+
## License
|
|
268
|
+
|
|
269
|
+
`package.json` currently declares **`UNLICENSED`**. No open-source license grant
|
|
270
|
+
is included in this repository.
|
package/README.tr.md
ADDED
|
@@ -0,0 +1,247 @@
|
|
|
1
|
+
# si-overnight
|
|
2
|
+
|
|
3
|
+
[English](https://github.com/siguelabs/si/blob/main/README.md) · **Türkçe**
|
|
4
|
+
|
|
5
|
+
**Uyumadan kararları ver. Agent, belirlediğin işleri uygulasın, test etsin ve sabaha rapor bıraksın.**
|
|
6
|
+
|
|
7
|
+
`si-overnight`, mevcut coding agent'ına gece çalışma düzeni kazandıran taşınabilir
|
|
8
|
+
bir [Agent Skill](https://agentskills.io/). Önce projeyi inceler, sen hâlâ
|
|
9
|
+
çevrimiçiyken gerekli soruları toplar; ardından kararlaştırılan kapsamda çalışır.
|
|
10
|
+
Codex, Claude Code, Google Antigravity ve pi için kurulum aracı içerir.
|
|
11
|
+
|
|
12
|
+

|
|
13
|
+
|
|
14
|
+
*GIF, çalışma adımlarını gösteren bir canlandırmadır. Alt agent kullanımı çalıştırdığın platformun desteğine bağlıdır.*
|
|
15
|
+
|
|
16
|
+
## Hızlı başlangıç
|
|
17
|
+
|
|
18
|
+
Node.js **20 veya üzeri** yeterli. Npm CLI'si Python veya ek runtime bağımlılığı
|
|
19
|
+
gerektirmez. Bu deponun kök dizininde:
|
|
20
|
+
|
|
21
|
+
```bash
|
|
22
|
+
# Önce kurulum hedeflerini gör.
|
|
23
|
+
node bin/si-overnight.mjs --platform all --project /tam/yol/projen --dry-run
|
|
24
|
+
|
|
25
|
+
# Seçtiğin projeye kur.
|
|
26
|
+
node bin/si-overnight.mjs --platform all --project /tam/yol/projen
|
|
27
|
+
|
|
28
|
+
# Ya da yalnız Codex için kullanıcı genelinde kur.
|
|
29
|
+
node bin/si-overnight.mjs --platform codex --scope user
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
`--project` mevcut bir dizin olmalıdır. Kurulumdan sonra hedef projeyi agent'ında
|
|
33
|
+
aç ve aşağıdaki platform komutlarından biriyle skill'i çağır.
|
|
34
|
+
|
|
35
|
+
### Npm üzerinden kurulum
|
|
36
|
+
|
|
37
|
+
En son yayımlanan sürümü kurmak için:
|
|
38
|
+
|
|
39
|
+
```bash
|
|
40
|
+
npx --yes si-overnight --platform all --project /tam/yol/projen
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
`npm install` tek başına skill'i agent dizinine kopyalamaz; kurulum CLI'sini
|
|
44
|
+
ayrıca çalıştırmalısın.
|
|
45
|
+
|
|
46
|
+
## Hangi platformda nasıl çağırılır?
|
|
47
|
+
|
|
48
|
+
| Platform | Skill'i çağırma | Proje içindeki kurulum dizini |
|
|
49
|
+
| --- | --- | --- |
|
|
50
|
+
| Codex | `$si-overnight` veya `/skills` içinden seç | `.agents/skills/si-overnight/` |
|
|
51
|
+
| Claude Code | `/si-overnight` | `.claude/skills/si-overnight/` |
|
|
52
|
+
| Google Antigravity | `/si-overnight` | `.agents/skills/si-overnight/` |
|
|
53
|
+
| pi | `/skill:si-overnight` | `.pi/skills/si-overnight/` |
|
|
54
|
+
|
|
55
|
+
Kullanıcı genelinde kurulum Codex için `~/.agents/skills/`, Claude Code için
|
|
56
|
+
`~/.claude/skills/`, Antigravity için `~/.gemini/config/skills/`, pi için
|
|
57
|
+
`~/.pi/agent/skills/` altında aynı `si-overnight/` klasörünü oluşturur.
|
|
58
|
+
|
|
59
|
+
Diğer Agent Skills uyumlu araçlarda `skills/si-overnight/` klasörünü aracın
|
|
60
|
+
belgelediği konuma kopyala. Dosya okuyabilen başka bir agente `SKILL.md` dosyasını
|
|
61
|
+
okuyup uygulamasını da söyleyebilirsin. Komutların ve alt agent desteğinin bütün
|
|
62
|
+
platformlarda aynı olduğu varsayılmaz.
|
|
63
|
+
|
|
64
|
+
## Bir gece nasıl ilerler?
|
|
65
|
+
|
|
66
|
+
### 1. Sen uyumadan önce
|
|
67
|
+
|
|
68
|
+
Agent önce proje talimatlarını, mevcut değişiklikleri ve test düzenini inceler.
|
|
69
|
+
Ardından cevabı projeden veya konuşmadan çıkmayan önemli soruları birlikte sorar:
|
|
70
|
+
|
|
71
|
+
- Ana hedefler, öncelikleri ve işin bittiğini gösterecek ölçütler.
|
|
72
|
+
- Bu gece **Liste** mi, **Keşif** mi kullanılacağı.
|
|
73
|
+
- Yedek işler veya keşfe izin verilen alanlar.
|
|
74
|
+
- Dokunulmayacak dosyalar, API davranışları ve tasarım kararları.
|
|
75
|
+
- Çalışma süresi veya saat dilimiyle birlikte bitiş saati; varsa bilinen bütçe.
|
|
76
|
+
- Beklenen testler, gerekli servisler ve erişimler.
|
|
77
|
+
- Teslim biçimi ve commit, PR veya deployment gibi işlemlere verilen yetkiler.
|
|
78
|
+
|
|
79
|
+
Bu gece için cevapladığın soruları yeniden sormaz. Gerekli kararlar tamamlanınca
|
|
80
|
+
kısa planı kaydeder ve ayrıca bir başlama onayı turu üretmeden işe geçer.
|
|
81
|
+
|
|
82
|
+
### 2. Gece modu seçilir
|
|
83
|
+
|
|
84
|
+
| Mod | Ana işler bitince | Ne zaman durur? |
|
|
85
|
+
| --- | --- | --- |
|
|
86
|
+
| **Liste / Queue** | Önceden kararlaştırılan yedek işleri yapar. | Onaylı liste bitince veya başka bir durma koşulu oluşunca. |
|
|
87
|
+
| **Keşif / Discover** | İzin verilen alanlarda kanıta dayalı iyileştirmeler bulur, önceliklendirir ve tek tek uygular. | Yararlı aday kalmayınca veya başka bir durma koşulu oluşunca. |
|
|
88
|
+
|
|
89
|
+
**Her yeni gece bu seçim yeniden sorulur.** Önceki gecenin modu kendiliğinden
|
|
90
|
+
taşınmaz. Kesilen aynı çalışmaya devam ederken mevcut gece sözleşmesi korunur.
|
|
91
|
+
|
|
92
|
+
Keşif modu için somut bir sınır örneği: “`src/cart/` ve `tests/cart/` içinde
|
|
93
|
+
doğrulanabilir bug fix ve regresyon testi yap; bağımlılık veya ödeme API'si
|
|
94
|
+
değiştirme.” Token tüketme isteği tek başına sınırsız proje kapsamı sayılmaz.
|
|
95
|
+
|
|
96
|
+
### 3. Uygula → test et → incele → kaydet
|
|
97
|
+
|
|
98
|
+
Agent sıradaki en önemli, engellenmemiş işi seçer; değişikliği yapar, uygun
|
|
99
|
+
testleri çalıştırır, sonucu inceler ve ilerlemeyi kaydeder. Anlamlı bir hata
|
|
100
|
+
kanıtı varsa düzeltir. Önceden bozuk testleri yeni hatalardan ayırır; çalışmayan
|
|
101
|
+
veya çalıştırılamayan kontrolü geçti diye raporlamaz.
|
|
102
|
+
|
|
103
|
+
Bir iş yeni bir karar ya da erişim gerektiriyorsa onu engeliyle birlikte kaydeder
|
|
104
|
+
ve bağımsız, yetkilendirilmiş işlere devam eder. Aynı engelde yeni kanıt olmadan
|
|
105
|
+
üç başarısız denemeden sonra başka işe geçer. Sırf token harcamak için aynı
|
|
106
|
+
başarılı testleri tekrar tekrar çalıştırmaz.
|
|
107
|
+
|
|
108
|
+
## Agent'lar nasıl birlikte çalışır?
|
|
109
|
+
|
|
110
|
+
Ana agent gece planının ve sonucun sahibidir. Platform alt agent destekliyorsa
|
|
111
|
+
bağımsız işler için görev dağıtabilir. Örneğin:
|
|
112
|
+
|
|
113
|
+
| Görev | Sorumluluk |
|
|
114
|
+
| --- | --- |
|
|
115
|
+
| Ana agent / koordinatör | Öncelikleri, kapsamı, süreyi ve son teslimi yönetir; sonuçları birleştirir. |
|
|
116
|
+
| Uygulama görevi | Kendi sorumluluğundaki dosyalarda belirli bir değişikliği yapar. |
|
|
117
|
+
| Test veya inceleme görevi | Bağımsız bir işi doğrular, regresyonları veya diff'teki somut sorunları inceler. |
|
|
118
|
+
|
|
119
|
+
Bu tablo sabit bir agent kadrosu tanımlamaz; görevler ihtiyaca göre seçilir.
|
|
120
|
+
Çakışan dosya yazımlarından kaçınılır, bütün çalışanlar aynı kapsam ve süreye
|
|
121
|
+
tabidir ve ana agent dönen sonuçları doğrular. Alt agent desteği yoksa aynı akış
|
|
122
|
+
tek agent ile yürütülür. Skill bu desteği platforma sonradan eklemez.
|
|
123
|
+
|
|
124
|
+
## Örnek gece isteği
|
|
125
|
+
|
|
126
|
+
Codex için:
|
|
127
|
+
|
|
128
|
+
```text
|
|
129
|
+
$si-overnight
|
|
130
|
+
Ana hedef: sepetteki doğrulanmış hataları düzelt ve regresyon testlerini ekle.
|
|
131
|
+
Bu gece Liste mi Keşif mi kullanacağımızı uyumadan bana sor.
|
|
132
|
+
Dokunma: ödeme API kontratları ve mevcut kullanıcı değişiklikleri.
|
|
133
|
+
En fazla 6 saat çalış. Teslim: yerel değişiklikler ve sabah raporu.
|
|
134
|
+
Gerekli diğer kararları ben çevrimiçiyken birlikte sor.
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
Diğer platformlarda ilk satırı o platformun çağırma komutuyla değiştir.
|
|
138
|
+
|
|
139
|
+
## Kayıtlar, sabah raporu ve devam etme
|
|
140
|
+
|
|
141
|
+
Her çalışma hedef projede ayrı bir klasöre yazılır:
|
|
142
|
+
|
|
143
|
+
```text
|
|
144
|
+
.si-overnight/
|
|
145
|
+
└── <run-id>/
|
|
146
|
+
├── run.md # Kapsam, kararlar, işler, son kontrol ve sıradaki adım
|
|
147
|
+
└── report.md # Tamamlananlar, test kanıtları, eksikler ve durma nedeni
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
Kayıtlar varsayılan olarak yerelde tutulur; açıkça istemedikçe commit'e alınmaz.
|
|
151
|
+
Skill sırf bu dosyaları gizlemek için `.gitignore` veya repo ayarlarını değiştirmez.
|
|
152
|
+
Gizli anahtarlar ve hassas komut çıktıları kayıtlara yazılmaz.
|
|
153
|
+
|
|
154
|
+
Devam örneği:
|
|
155
|
+
|
|
156
|
+
```text
|
|
157
|
+
$si-overnight
|
|
158
|
+
.si-overnight/<run-id>/run.md dosyasındaki çalışmaya devam et.
|
|
159
|
+
Önce kaydı mevcut dosyalarla karşılaştır. Aynı kapsamı koru.
|
|
160
|
+
Eski süre dolduysa bu andan itibaren 2 saatlik yeni pencere kullan.
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
Agent bir komutun kesintiden önce başarıyla bittiğini varsaymaz; mevcut dosyaları,
|
|
164
|
+
sonuçları ve diğer kişilerin değişikliklerini kayıtla karşılaştırır.
|
|
165
|
+
|
|
166
|
+
## Çalışma ne zaman biter?
|
|
167
|
+
|
|
168
|
+
Onaylı işler bittiğinde, kapsam içinde yararlı keşif kalmadığında, süre veya
|
|
169
|
+
gözlemlenebilir kota sınırı dolduğunda, bütün kalan işler engellendiğinde ya da sen
|
|
170
|
+
durmasını istediğinde çalışmayı sonlandırır. Ölçülemeyen kalan kotayı tahmin diye
|
|
171
|
+
sunmaz.
|
|
172
|
+
|
|
173
|
+
**Skill bir süreç yöneticisi değildir.** Bilgisayarı uyanık tutmaz, kapanan agent'ı
|
|
174
|
+
yeniden başlatmaz, yeni model turları oluşturmaz veya kota yenilemez. Yerel
|
|
175
|
+
makine/oturum veya gerçekten uzakta çalışan ortam kullanılabilir kalmalıdır.
|
|
176
|
+
Ani kesintide son kayıttan devam edilebilir; durmuş süreç sonradan rapor yazamaz.
|
|
177
|
+
Host'un uzun çalışma özelliği ayrıca kullanılabilir; bu skill kendiliğinden bir
|
|
178
|
+
Goal, zamanlanmış görev veya arka plan runner'ı oluşturmaz.
|
|
179
|
+
|
|
180
|
+
## CLI seçenekleri ve Python alternatifi
|
|
181
|
+
|
|
182
|
+
| Seçenek | Değer / davranış |
|
|
183
|
+
| --- | --- |
|
|
184
|
+
| `--platform` | `codex`, `claude`, `antigravity`, `pi` veya `all`; zorunlu. |
|
|
185
|
+
| `--scope` | `project` (varsayılan) veya `user`. |
|
|
186
|
+
| `--project` | Mevcut proje dizini; varsayılan geçerli dizin. Kullanıcı kapsamını değiştirmez. |
|
|
187
|
+
| `--dry-run` | Hedefleri gösterir, dosya yazmaz. |
|
|
188
|
+
| `--help` | Yardımı gösterir. |
|
|
189
|
+
|
|
190
|
+
Npm CLI'sinde birden fazla platform için bayrağı tekrarla:
|
|
191
|
+
|
|
192
|
+
```bash
|
|
193
|
+
node bin/si-overnight.mjs --platform claude --platform pi --dry-run
|
|
194
|
+
```
|
|
195
|
+
|
|
196
|
+
Kurucu farklı bir mevcut skill'in üzerine yazmaz; içerik aynıysa dosyaları
|
|
197
|
+
değiştirmez. Seçtiğin kökün altındaki kurulum yollarında sembolik bağlantılar
|
|
198
|
+
reddedilir. Açıkça seçilen kökün kendisi bir dizin takma adı olabilir. Güncellemede
|
|
199
|
+
mevcut kurulumu inceleyip taşıdıktan sonra yeniden kur. Kurulum agent izinlerini
|
|
200
|
+
değiştirmez veya çalışmayı başlatmaz.
|
|
201
|
+
|
|
202
|
+
Kaynak kod deposunda Python 3 alternatifi de bulunur:
|
|
203
|
+
|
|
204
|
+
```bash
|
|
205
|
+
python3 scripts/install.py --platform all --project /tam/yol/projen
|
|
206
|
+
```
|
|
207
|
+
|
|
208
|
+
## Geliştirme ve sürüm yayımlama
|
|
209
|
+
|
|
210
|
+
```bash
|
|
211
|
+
npm test
|
|
212
|
+
python3 -m unittest discover -s tests -v
|
|
213
|
+
node .github/scripts/pack-smoke.mjs /tmp/si-overnight-package-check
|
|
214
|
+
```
|
|
215
|
+
|
|
216
|
+
Son komutun çıktı dizini boş olmalıdır. Gerçek `.tgz` dosyasını boş npm cache'iyle
|
|
217
|
+
çevrimdışı kurar, CLI'yi ve skill dosyalarının byte eşitliğini kontrol eder.
|
|
218
|
+
|
|
219
|
+
README'deki canlandırmayı yeniden oluşturmak için `python3 scripts/render_workflow.py`
|
|
220
|
+
çalıştır. Bu geliştirme aracı Pillow gerektirir; npm kurucusunun runtime bağımlılığı
|
|
221
|
+
değildir.
|
|
222
|
+
|
|
223
|
+
CI her branch push'unda ve PR'da Node.js 20/24 ile testleri çalıştırır; paket ve
|
|
224
|
+
SHA-256 özeti `npm-package` artifact'i olarak hazırlanır. Sürümle eşleşen
|
|
225
|
+
`vMAJOR.MINOR.PATCH` etiketi, testler geçtikten sonra aynı paketi npm'e yayımlar.
|
|
226
|
+
Ön sürüm etiketleri mevcut release akışında desteklenmez.
|
|
227
|
+
|
|
228
|
+
İlk npm kaydı için hesabın yayın yetkisi gerekir. Staged bir sürüm varsa npm
|
|
229
|
+
profilindeki **Staged Packages** üzerinden inceleyip 2FA ile onayla. Yayımlanmış
|
|
230
|
+
aynı isim/sürüm yeniden kullanılamaz. [Staged publishing belgesi](https://docs.npmjs.com/staged-publishing/).
|
|
231
|
+
|
|
232
|
+
Otomatik yayın için paket **Settings → Trusted publishing → GitHub Actions**
|
|
233
|
+
ayarında owner `siguelabs`, repo `si`, workflow `release.yml`, environment boş ve
|
|
234
|
+
**Allow npm publish** açık olmalıdır. Bu OIDC akışı `NPM_TOKEN` secret'ı
|
|
235
|
+
gerektirmez. Yeni bağlantının ilk yayını iki gün içinde yapılmalıdır. Provenance
|
|
236
|
+
için kaynak repo public ve `repository.url` aynı GitHub deposuna bağlı olmalıdır.
|
|
237
|
+
Yayın işi Node.js 24 ve npm ≥11.5.1 kullanır/kontrol eder.
|
|
238
|
+
[Trusted publishing belgesi](https://docs.npmjs.com/trusted-publishers/).
|
|
239
|
+
|
|
240
|
+
Kod yapısı: `skills/si-overnight/` ortak çalışma talimatlarını, `bin/` ve `lib/`
|
|
241
|
+
Node kurucusunu, `scripts/install.py` Python alternatifini, `tests/` kontrolleri,
|
|
242
|
+
`.github/` CI ve release akışlarını içerir. Platformlara ilişkin resmi kaynaklar
|
|
243
|
+
[uyumluluk notlarında](skills/si-overnight/references/platforms.md) bulunur.
|
|
244
|
+
|
|
245
|
+
Katkı yaparken kurucu değişikliklerini ilgili testlerle doğrula; çalışma akışı
|
|
246
|
+
değişikliklerinde iki dildeki README'yi birlikte güncelle. Paket şu anda
|
|
247
|
+
**`UNLICENSED`** olarak tanımlıdır; açık kaynak kullanım lisansı verilmemiştir.
|
|
@@ -0,0 +1,48 @@
|
|
|
1
|
+
#!/usr/bin/env node
|
|
2
|
+
|
|
3
|
+
import { parseArgs } from 'node:util';
|
|
4
|
+
import { installSkill } from '../lib/install.mjs';
|
|
5
|
+
|
|
6
|
+
const help = `Usage: si-overnight --platform <name> [options]
|
|
7
|
+
|
|
8
|
+
Install the si-overnight skill. No agent process or background job is started.
|
|
9
|
+
|
|
10
|
+
Options:
|
|
11
|
+
--platform <name> codex, claude, antigravity, pi, or all (repeatable)
|
|
12
|
+
--scope <scope> project (default) or user
|
|
13
|
+
--project <path> Existing target project directory (default: current directory)
|
|
14
|
+
--dry-run Show destinations without writing files
|
|
15
|
+
--help, -h Show this help
|
|
16
|
+
|
|
17
|
+
Examples:
|
|
18
|
+
si-overnight --platform all --project /path/to/project
|
|
19
|
+
si-overnight --platform codex --scope user
|
|
20
|
+
si-overnight --platform claude --platform pi --dry-run
|
|
21
|
+
`;
|
|
22
|
+
|
|
23
|
+
try {
|
|
24
|
+
const { values } = parseArgs({
|
|
25
|
+
options: {
|
|
26
|
+
platform: { type: 'string', multiple: true },
|
|
27
|
+
scope: { type: 'string', default: 'project' },
|
|
28
|
+
project: { type: 'string' },
|
|
29
|
+
'dry-run': { type: 'boolean', default: false },
|
|
30
|
+
help: { type: 'boolean', short: 'h' },
|
|
31
|
+
},
|
|
32
|
+
strict: true,
|
|
33
|
+
allowPositionals: false,
|
|
34
|
+
});
|
|
35
|
+
if (values.help) {
|
|
36
|
+
process.stdout.write(help);
|
|
37
|
+
} else {
|
|
38
|
+
installSkill({
|
|
39
|
+
platforms: values.platform,
|
|
40
|
+
scope: values.scope,
|
|
41
|
+
project: values.project,
|
|
42
|
+
dryRun: values['dry-run'],
|
|
43
|
+
});
|
|
44
|
+
}
|
|
45
|
+
} catch (error) {
|
|
46
|
+
console.error(`Install failed: ${error.message}`);
|
|
47
|
+
process.exitCode = 1;
|
|
48
|
+
}
|
|
Binary file
|
package/lib/install.mjs
ADDED
|
@@ -0,0 +1,151 @@
|
|
|
1
|
+
import {
|
|
2
|
+
lstatSync, mkdirSync, readdirSync, readFileSync, realpathSync, writeFileSync,
|
|
3
|
+
} from 'node:fs';
|
|
4
|
+
import { homedir } from 'node:os';
|
|
5
|
+
import { dirname, isAbsolute, join, relative, resolve, sep } from 'node:path';
|
|
6
|
+
import { fileURLToPath } from 'node:url';
|
|
7
|
+
|
|
8
|
+
export const SKILL_SOURCE = fileURLToPath(new URL('../skills/si-overnight/', import.meta.url));
|
|
9
|
+
const PROJECT_PATHS = {
|
|
10
|
+
codex: '.agents/skills',
|
|
11
|
+
claude: '.claude/skills',
|
|
12
|
+
antigravity: '.agents/skills',
|
|
13
|
+
pi: '.pi/skills',
|
|
14
|
+
};
|
|
15
|
+
const USER_PATHS = {
|
|
16
|
+
codex: '.agents/skills',
|
|
17
|
+
claude: '.claude/skills',
|
|
18
|
+
antigravity: '.gemini/config/skills',
|
|
19
|
+
pi: '.pi/agent/skills',
|
|
20
|
+
};
|
|
21
|
+
|
|
22
|
+
function inspect(path) {
|
|
23
|
+
try {
|
|
24
|
+
return lstatSync(path);
|
|
25
|
+
} catch (error) {
|
|
26
|
+
if (error.code === 'ENOENT') return undefined;
|
|
27
|
+
throw error;
|
|
28
|
+
}
|
|
29
|
+
}
|
|
30
|
+
|
|
31
|
+
function within(root, path) {
|
|
32
|
+
const suffix = relative(root, path);
|
|
33
|
+
return suffix === '' || (!isAbsolute(suffix) && suffix !== '..' && !suffix.startsWith(`..${sep}`));
|
|
34
|
+
}
|
|
35
|
+
|
|
36
|
+
function snapshot(directory) {
|
|
37
|
+
const result = new Map();
|
|
38
|
+
const visit = (path, name) => {
|
|
39
|
+
const stat = inspect(path);
|
|
40
|
+
if (!stat || stat.isSymbolicLink()) throw new Error(`Missing path or symbolic link: ${path}`);
|
|
41
|
+
if (stat.isDirectory()) {
|
|
42
|
+
result.set(name, null);
|
|
43
|
+
for (const child of readdirSync(path).sort()) visit(join(path, child), join(name, child));
|
|
44
|
+
} else if (stat.isFile()) {
|
|
45
|
+
result.set(name, readFileSync(path));
|
|
46
|
+
} else {
|
|
47
|
+
throw new Error(`Expected a regular file or directory: ${path}`);
|
|
48
|
+
}
|
|
49
|
+
};
|
|
50
|
+
visit(directory, '');
|
|
51
|
+
return result;
|
|
52
|
+
}
|
|
53
|
+
|
|
54
|
+
function equalSnapshots(first, second) {
|
|
55
|
+
if (first.size !== second.size) return false;
|
|
56
|
+
for (const [name, content] of first) {
|
|
57
|
+
if (!second.has(name)) return false;
|
|
58
|
+
const other = second.get(name);
|
|
59
|
+
if (content === null ? other !== null : other === null || !content.equals(other)) return false;
|
|
60
|
+
}
|
|
61
|
+
return true;
|
|
62
|
+
}
|
|
63
|
+
|
|
64
|
+
function checkParents(root, destination) {
|
|
65
|
+
if (!within(root, destination) || destination === root) throw new Error('Destination must be inside the selected root.');
|
|
66
|
+
let path = root;
|
|
67
|
+
const pieces = relative(root, destination).split(sep);
|
|
68
|
+
for (const piece of pieces) {
|
|
69
|
+
path = join(path, piece);
|
|
70
|
+
const stat = inspect(path);
|
|
71
|
+
if (!stat) continue;
|
|
72
|
+
if (stat.isSymbolicLink() || !stat.isDirectory()) {
|
|
73
|
+
throw new Error(`Refusing a symbolic link or non-directory in destination path: ${path}`);
|
|
74
|
+
}
|
|
75
|
+
}
|
|
76
|
+
}
|
|
77
|
+
|
|
78
|
+
function ensureParents(root, destination) {
|
|
79
|
+
let path = root;
|
|
80
|
+
for (const piece of relative(root, dirname(destination)).split(sep)) {
|
|
81
|
+
path = join(path, piece);
|
|
82
|
+
try {
|
|
83
|
+
mkdirSync(path);
|
|
84
|
+
} catch (error) {
|
|
85
|
+
if (error.code !== 'EEXIST') throw error;
|
|
86
|
+
}
|
|
87
|
+
const stat = lstatSync(path);
|
|
88
|
+
if (stat.isSymbolicLink() || !stat.isDirectory()) throw new Error(`Unsafe destination parent: ${path}`);
|
|
89
|
+
}
|
|
90
|
+
}
|
|
91
|
+
|
|
92
|
+
export function installationTargets({ platforms, scope = 'project', project = process.cwd(), userHome = homedir() }) {
|
|
93
|
+
if (!Array.isArray(platforms) || platforms.length === 0) throw new Error('--platform is required.');
|
|
94
|
+
for (const platform of platforms) {
|
|
95
|
+
if (platform !== 'all' && !Object.hasOwn(PROJECT_PATHS, platform)) throw new Error(`Unknown platform: ${platform}`);
|
|
96
|
+
}
|
|
97
|
+
if (scope !== 'project' && scope !== 'user') throw new Error('--scope must be project or user.');
|
|
98
|
+
const paths = scope === 'project' ? PROJECT_PATHS : USER_PATHS;
|
|
99
|
+
const root = realpathSync(resolve(scope === 'project' ? project : userHome));
|
|
100
|
+
if (!lstatSync(root).isDirectory()) throw new Error(`Selected root is not a directory: ${root}`);
|
|
101
|
+
const names = platforms.includes('all') ? Object.keys(paths) : platforms;
|
|
102
|
+
return { root, destinations: [...new Set(names.map((name) => join(root, paths[name], 'si-overnight')))] };
|
|
103
|
+
}
|
|
104
|
+
|
|
105
|
+
export function installSkill({
|
|
106
|
+
platforms, scope = 'project', project = process.cwd(), userHome = homedir(),
|
|
107
|
+
dryRun = false, source = SKILL_SOURCE, log = console.log,
|
|
108
|
+
} = {}) {
|
|
109
|
+
const { root, destinations } = installationTargets({ platforms, scope, project, userHome });
|
|
110
|
+
const sourcePath = resolve(source);
|
|
111
|
+
const expected = snapshot(sourcePath);
|
|
112
|
+
if (!Buffer.isBuffer(expected.get('SKILL.md'))) throw new Error(`Missing source SKILL.md: ${sourcePath}`);
|
|
113
|
+
const canonicalSource = realpathSync(sourcePath);
|
|
114
|
+
const pending = new Set();
|
|
115
|
+
|
|
116
|
+
// Check every destination before creating anything, including shared host paths.
|
|
117
|
+
for (const destination of destinations) {
|
|
118
|
+
if (within(canonicalSource, destination) || within(destination, canonicalSource)) {
|
|
119
|
+
throw new Error(`Source and destination overlap: ${destination}`);
|
|
120
|
+
}
|
|
121
|
+
checkParents(root, destination);
|
|
122
|
+
if (inspect(destination)) {
|
|
123
|
+
if (!equalSnapshots(expected, snapshot(destination))) {
|
|
124
|
+
throw new Error(`Existing destination differs; nothing overwritten: ${destination}`);
|
|
125
|
+
}
|
|
126
|
+
} else {
|
|
127
|
+
pending.add(destination);
|
|
128
|
+
}
|
|
129
|
+
}
|
|
130
|
+
|
|
131
|
+
for (const destination of destinations) {
|
|
132
|
+
if (!pending.has(destination)) {
|
|
133
|
+
log(`Already installed: ${destination}`);
|
|
134
|
+
} else if (dryRun) {
|
|
135
|
+
log(`Would install: ${destination}`);
|
|
136
|
+
} else {
|
|
137
|
+
checkParents(root, destination);
|
|
138
|
+
ensureParents(root, destination);
|
|
139
|
+
// Exclusive mkdir/write prevents merging into or overwriting a destination.
|
|
140
|
+
mkdirSync(destination);
|
|
141
|
+
for (const [name, content] of expected) {
|
|
142
|
+
if (name === '') continue;
|
|
143
|
+
const path = join(destination, name);
|
|
144
|
+
if (content === null) mkdirSync(path);
|
|
145
|
+
else writeFileSync(path, content, { flag: 'wx', mode: 0o644 });
|
|
146
|
+
}
|
|
147
|
+
log(`Installed: ${destination}`);
|
|
148
|
+
}
|
|
149
|
+
}
|
|
150
|
+
return destinations;
|
|
151
|
+
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,36 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "si-overnight",
|
|
3
|
-
"version": "0.
|
|
4
|
-
"
|
|
5
|
-
"
|
|
6
|
-
|
|
3
|
+
"version": "0.1.1",
|
|
4
|
+
"description": "Install a portable overnight coding workflow for Codex, Claude Code, Antigravity, and pi.",
|
|
5
|
+
"repository": {
|
|
6
|
+
"type": "git",
|
|
7
|
+
"url": "git+https://github.com/siguelabs/si.git"
|
|
8
|
+
},
|
|
9
|
+
"type": "module",
|
|
10
|
+
"bin": {
|
|
11
|
+
"si-overnight": "bin/si-overnight.mjs"
|
|
12
|
+
},
|
|
13
|
+
"files": [
|
|
14
|
+
"bin/",
|
|
15
|
+
"lib/",
|
|
16
|
+
"skills/si-overnight/",
|
|
17
|
+
"README.md",
|
|
18
|
+
"README.tr.md",
|
|
19
|
+
"docs/assets/overnight-workflow.gif"
|
|
20
|
+
],
|
|
21
|
+
"engines": {
|
|
22
|
+
"node": ">=20"
|
|
23
|
+
},
|
|
24
|
+
"scripts": {
|
|
25
|
+
"test": "node --test tests/*.test.mjs"
|
|
26
|
+
},
|
|
27
|
+
"keywords": [
|
|
28
|
+
"agent-skills",
|
|
29
|
+
"codex",
|
|
30
|
+
"claude-code",
|
|
31
|
+
"antigravity",
|
|
32
|
+
"pi",
|
|
33
|
+
"overnight"
|
|
34
|
+
],
|
|
35
|
+
"license": "UNLICENSED"
|
|
36
|
+
}
|
|
@@ -0,0 +1,179 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: si-overnight
|
|
3
|
+
description: Prepare and execute unattended overnight coding work. Interview the user before they leave, choose a fixed queue or scoped improvement discovery, implement and test, checkpoint progress, and leave a morning report. Use when the user asks to keep working while they sleep or invokes si-overnight.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# SI Overnight
|
|
7
|
+
|
|
8
|
+
Turn the user's available agent time into finished, verified project work while
|
|
9
|
+
they are away. Use the user's language for questions, checkpoints, and reports.
|
|
10
|
+
|
|
11
|
+
This skill supplies a workflow, not a background process. It cannot keep a
|
|
12
|
+
computer awake, restart an agent, create new turns after the host stops, bypass
|
|
13
|
+
approvals, or extend a provider quota. Explain relevant limitations once before
|
|
14
|
+
the user leaves. Use the host's existing execution facilities; do not silently
|
|
15
|
+
install a supervisor, schedule jobs, or weaken permission settings. For setup or
|
|
16
|
+
invocation differences, read [references/platforms.md](references/platforms.md).
|
|
17
|
+
|
|
18
|
+
## 1. Inspect before interviewing
|
|
19
|
+
|
|
20
|
+
Read applicable project instructions and inspect the current workspace, existing
|
|
21
|
+
changes, task context, build scripts, test setup, and available tools. Identify
|
|
22
|
+
likely blockers without reading secret values. Do not start implementation yet.
|
|
23
|
+
Check whether a previous overnight run is being resumed before creating a new one.
|
|
24
|
+
|
|
25
|
+
Ask only consequential questions that inspection and the current conversation do
|
|
26
|
+
not answer. Batch them so the user can answer before sleeping. Use the host's
|
|
27
|
+
question tool when available, otherwise a concise numbered message.
|
|
28
|
+
|
|
29
|
+
For **every new overnight run**, explicitly ask which mode to use, unless the
|
|
30
|
+
user has already chosen for this run:
|
|
31
|
+
|
|
32
|
+
- **Queue:** Finish the agreed primary tasks, then the agreed backup tasks, then
|
|
33
|
+
stop. Do not invent additional implementation work.
|
|
34
|
+
- **Discover:** Finish the primary tasks, then find and implement useful
|
|
35
|
+
improvements within agreed project areas, categories, and exclusions.
|
|
36
|
+
|
|
37
|
+
Neither mode is a permanent preference. Do not silently inherit last night's
|
|
38
|
+
mode. On a resume, retain this run's mode and ask only about material changes.
|
|
39
|
+
|
|
40
|
+
Resolve the following in the same interview, reusing explicit answers:
|
|
41
|
+
|
|
42
|
+
- Primary outcomes, priority, and observable acceptance criteria. Offer concrete
|
|
43
|
+
candidates from the project if the user has not supplied tasks.
|
|
44
|
+
- Backup tasks for Queue; allowed areas and kinds of improvement for Discover.
|
|
45
|
+
Ask whether dependency changes or broad refactors are included when relevant.
|
|
46
|
+
- Paths, behavior, APIs, data, or design decisions that must remain unchanged.
|
|
47
|
+
- A stop time with date and timezone, or a duration; any known spend/token cap.
|
|
48
|
+
Offer a bounded duration if the user has no preference. Do not invent a cap.
|
|
49
|
+
- The expected checks and available test environment. Identify missing credentials,
|
|
50
|
+
services, network access, dependencies, and anticipated permission prompts now.
|
|
51
|
+
- Delivery expectations and permissions that matter for these tasks: local edits,
|
|
52
|
+
commits, push/PR, deployments, migrations, or external services. Propose local
|
|
53
|
+
edits and a report for unspecified delivery. Reuse existing authorization.
|
|
54
|
+
|
|
55
|
+
In Discover mode, propose a concrete discovery boundary, such as bug fixes,
|
|
56
|
+
regression tests, and small accessibility improvements in named directories.
|
|
57
|
+
"Use all my tokens" expresses willingness to work; it does not define a project
|
|
58
|
+
scope. Do not accept unbounded unrelated work as a substitute for scope.
|
|
59
|
+
|
|
60
|
+
If questions are pending, continue useful read-only preparation. Do not treat
|
|
61
|
+
silence, elapsed time, or the user going offline as an answer. If a question only
|
|
62
|
+
affects an optional branch, defer that branch and proceed with independently
|
|
63
|
+
authorized work. A bare invocation with no actionable scope must stay in intake.
|
|
64
|
+
|
|
65
|
+
## 2. Save the run contract and start
|
|
66
|
+
|
|
67
|
+
Use [references/run-template.md](references/run-template.md) to create a compact
|
|
68
|
+
`.si-overnight/<unique-run-id>/run.md` in the target project. Use a timestamp plus
|
|
69
|
+
a collision suffix if needed. Preserve existing runs. Record the workspace,
|
|
70
|
+
baseline changes, chosen mode, exact scope, user answers, authorization, deadline,
|
|
71
|
+
acceptance criteria, task order, test plan, and next action. Never save credentials.
|
|
72
|
+
|
|
73
|
+
Show a short resolved plan and begin as soon as the necessary answers are in.
|
|
74
|
+
The user's answers are the go-ahead for the agreed work; do not add a ceremonial
|
|
75
|
+
"may I start?" round. If the user explicitly says wait, wait.
|
|
76
|
+
|
|
77
|
+
Before they leave, run proportionate baseline checks and a representative command
|
|
78
|
+
that exercises the expected permissions. Surface concrete setup blockers while
|
|
79
|
+
they can still answer. Do not promise that preflight prevents all future prompts.
|
|
80
|
+
Preserve existing user edits; use an isolated branch/worktree when appropriate
|
|
81
|
+
and supported, checking that its environment works. Never reset or stash user
|
|
82
|
+
changes merely to obtain a clean tree.
|
|
83
|
+
|
|
84
|
+
Keep the run files local and exclude them from staging unless the user asks to
|
|
85
|
+
version them. Do not change repository ignore/configuration files just to hide
|
|
86
|
+
these artifacts. If checkpoints cannot be written, disclose the limitation and
|
|
87
|
+
use an available approved persistent location; do not claim durable recovery.
|
|
88
|
+
|
|
89
|
+
## 3. Execute without requiring a conversation
|
|
90
|
+
|
|
91
|
+
Repeat while useful authorized work and budget remain:
|
|
92
|
+
|
|
93
|
+
1. Read the checkpoint and check the current time, scope, and available budget.
|
|
94
|
+
Reserve enough remaining time for verification and a handoff. If the host
|
|
95
|
+
exposes reliable usage telemetry, use it; otherwise report quota as unknown.
|
|
96
|
+
2. Select the highest-priority unblocked task. Keep tasks small enough to verify
|
|
97
|
+
independently. Resolve ordinary implementation choices using the contract
|
|
98
|
+
and project conventions instead of asking the absent user.
|
|
99
|
+
3. Implement the change and add meaningful regression coverage where warranted.
|
|
100
|
+
Use bounded, noninteractive commands; avoid watch modes, interactive prompts,
|
|
101
|
+
and commands that wait indefinitely. Stop only processes started by this run.
|
|
102
|
+
4. Run focused checks, fix demonstrated regressions, and run the broader checks
|
|
103
|
+
required by the project or the acceptance criteria. Distinguish baseline
|
|
104
|
+
failures from new failures and unavailable checks from passing checks.
|
|
105
|
+
5. Review the resulting diff for correctness, scope, and unrelated changes.
|
|
106
|
+
Record the evidence and next action before moving to the next task.
|
|
107
|
+
|
|
108
|
+
Use available subagents for independent work when it helps; assign nonoverlapping
|
|
109
|
+
write ownership and verify their outputs. Do not assume every host supports them.
|
|
110
|
+
The same scope, deadline, and permissions apply to every worker.
|
|
111
|
+
|
|
112
|
+
Do not end with "I can continue if you want" while authorized work remains.
|
|
113
|
+
Continue within the active execution until completion, a stop condition, or a
|
|
114
|
+
host limit. A progress message is not a handoff requiring the user to reply.
|
|
115
|
+
|
|
116
|
+
In **Queue** mode, consume only the approved primary and backup queues.
|
|
117
|
+
In **Discover** mode, inspect for evidence-backed candidates after the primary
|
|
118
|
+
queue, rank by user impact and confidence, and implement one bounded improvement
|
|
119
|
+
at a time. Record each candidate's evidence, fit with the agreed scope, and
|
|
120
|
+
acceptance check before editing. Prefer reproducible bugs, missing regression
|
|
121
|
+
coverage, and improvements with observable benefit over speculative rewrites.
|
|
122
|
+
If no worthwhile candidate remains, stop and report that fact.
|
|
123
|
+
|
|
124
|
+
Run tests to obtain evidence, not to spend tokens. Do not disable tests, loosen
|
|
125
|
+
assertions, hide diagnostics, or change product requirements to manufacture a
|
|
126
|
+
pass. Do not repeatedly rerun unchanged passing checks without a new reason.
|
|
127
|
+
|
|
128
|
+
## 4. Handle surprises and stop conditions
|
|
129
|
+
|
|
130
|
+
When a task needs a new consequential decision, unavailable access, or an action
|
|
131
|
+
outside the contract, record the precise blocker and continue independent
|
|
132
|
+
authorized work. If a runtime approval is required, follow the host's approval
|
|
133
|
+
mechanism; prior agreement does not override it. Do not block the entire queue
|
|
134
|
+
on an optional deployment or credential-dependent integration.
|
|
135
|
+
|
|
136
|
+
Permission to discover improvements does not add permission to publish, deploy,
|
|
137
|
+
send messages, spend money, access new sensitive data, or alter unrelated projects.
|
|
138
|
+
Perform such actions only with applicable explicit authorization and host approval.
|
|
139
|
+
Never weaken sandboxing, permissions, tests, or security controls to keep running.
|
|
140
|
+
|
|
141
|
+
After three failed attempts on the same blocker without meaningful new evidence,
|
|
142
|
+
checkpoint it and move to another task. Retry transient failures only with bounded
|
|
143
|
+
backoff inside the remaining budget; do not wait indefinitely for quota resets.
|
|
144
|
+
|
|
145
|
+
Stop when any of these holds:
|
|
146
|
+
|
|
147
|
+
- The chosen queue is complete, or scoped discovery has no worthwhile work left.
|
|
148
|
+
- The agreed deadline or an observable budget/provider limit is reached.
|
|
149
|
+
- All remaining work depends on unavailable access, approval, or a user decision.
|
|
150
|
+
- The user asks to stop, or the host ends execution.
|
|
151
|
+
|
|
152
|
+
Checkpoint after every completed task, material failed attempt, permission blocker,
|
|
153
|
+
and before a risky operation or context handoff. Include work in progress and its
|
|
154
|
+
verification state. On foreseeable shutdown or quota exhaustion, save the report
|
|
155
|
+
if possible. A sudden termination may leave only the last checkpoint; never
|
|
156
|
+
promise an after-the-fact report from a stopped process.
|
|
157
|
+
|
|
158
|
+
## 5. Resume and leave the morning report
|
|
159
|
+
|
|
160
|
+
On resume, read the contract, checkpoint, current instructions, workspace diff,
|
|
161
|
+
and recent changes before acting. Reconcile the files with the recorded state;
|
|
162
|
+
do not assume an interrupted command succeeded. Check for other actors' edits.
|
|
163
|
+
Do not redo completed work or silently expand scope. If the deadline has expired,
|
|
164
|
+
write a handoff and obtain a new execution window before more implementation.
|
|
165
|
+
If a new approval is needed, preserve progress and identify the affected task.
|
|
166
|
+
|
|
167
|
+
Write `.si-overnight/<run-id>/report.md` in the user's language and give a short
|
|
168
|
+
chat handoff linking it. Report:
|
|
169
|
+
|
|
170
|
+
- Completed outcomes and their acceptance evidence.
|
|
171
|
+
- Changed files and any commits/PRs actually created under the agreed permissions.
|
|
172
|
+
- Exact check commands, observed outcomes, and checks that could not run.
|
|
173
|
+
- Incomplete work, blockers, assumptions, and any unverified changes.
|
|
174
|
+
- Why execution stopped, remaining useful work, and one concrete resume prompt
|
|
175
|
+
naming this run's `run.md`.
|
|
176
|
+
|
|
177
|
+
Mark completion only when the relevant acceptance criteria are satisfied. Leave
|
|
178
|
+
blocked or unverified work clearly identified. Never claim all available tokens
|
|
179
|
+
were consumed without reliable measurement.
|
|
@@ -0,0 +1,56 @@
|
|
|
1
|
+
# Host compatibility
|
|
2
|
+
|
|
3
|
+
The same `SKILL.md` implements the workflow. Installation and invocation differ
|
|
4
|
+
by host. These paths and commands were checked against official documentation on
|
|
5
|
+
2026-11-17; installed versions and organization settings can differ.
|
|
6
|
+
|
|
7
|
+
| Host | Project skill directory | User skill directory | Invocation |
|
|
8
|
+
| --- | --- | --- | --- |
|
|
9
|
+
| Codex | `.agents/skills/si-overnight/` | `~/.agents/skills/si-overnight/` | `$si-overnight` or select via `/skills` |
|
|
10
|
+
| Claude Code | `.claude/skills/si-overnight/` | `~/.claude/skills/si-overnight/` | `/si-overnight` |
|
|
11
|
+
| Google Antigravity | `.agents/skills/si-overnight/` | `~/.gemini/config/skills/si-overnight/` | `/si-overnight` |
|
|
12
|
+
| pi | `.pi/skills/si-overnight/` | `~/.pi/agent/skills/si-overnight/` | `/skill:si-overnight` |
|
|
13
|
+
|
|
14
|
+
Each directory contains `SKILL.md` and its supporting files. Pi also supports
|
|
15
|
+
`.agents/skills` and `~/.agents/skills`. Antigravity retains legacy `.agent/skills`
|
|
16
|
+
compatibility; use the current path for new installations.
|
|
17
|
+
|
|
18
|
+
Do not promise a literal `/si-overnight` command on every platform. On other
|
|
19
|
+
Agent Skills-compatible hosts, use that host's documented discovery path and
|
|
20
|
+
invocation mechanism. If skills are unsupported but file reading and editing are
|
|
21
|
+
available, the user can explicitly ask the agent to read this `SKILL.md` and
|
|
22
|
+
follow it; native command registration is not implied.
|
|
23
|
+
|
|
24
|
+
## Execution lifetime
|
|
25
|
+
|
|
26
|
+
The user must leave a usable execution environment: the local machine, agent
|
|
27
|
+
process, session, and required services must remain available, or the host must
|
|
28
|
+
provide an actual remote execution environment. A checkpoint makes a later
|
|
29
|
+
resume possible; it does not trigger that resume.
|
|
30
|
+
|
|
31
|
+
An instruction-only skill does not provide an autonomous process supervisor.
|
|
32
|
+
Headless/print commands normally complete a request and exit. Re-launching them
|
|
33
|
+
requires a separate, explicitly configured runner with its own bounds and
|
|
34
|
+
permissions. This skill does not install one or automatically retry billing and
|
|
35
|
+
quota failures. Do not claim that a successful process exit proves tests passed.
|
|
36
|
+
|
|
37
|
+
Codex versions exposing Goal mode can support sustained work through `/goal`.
|
|
38
|
+
The user can explicitly start a goal containing the agreed overnight contract.
|
|
39
|
+
Do not assume that invoking this skill creates a native goal or schedule, or that
|
|
40
|
+
Goal mode removes quota, access, or environment limits.
|
|
41
|
+
|
|
42
|
+
Use supported host question/approval tools and preserve the user's configured
|
|
43
|
+
permission policy. Do not prescribe blanket permission bypass flags for unattended
|
|
44
|
+
execution. Anticipated access should be checked during the awake interview.
|
|
45
|
+
|
|
46
|
+
Sources:
|
|
47
|
+
|
|
48
|
+
- [Codex skills](https://learn.chatgpt.com/docs/build-skills)
|
|
49
|
+
- [Codex long-running work](https://learn.chatgpt.com/docs/long-running-work)
|
|
50
|
+
- [Claude Code skills](https://code.claude.com/docs/en/skills)
|
|
51
|
+
- [Claude Code headless execution](https://code.claude.com/docs/en/headless)
|
|
52
|
+
- [Antigravity skills](https://antigravity.google/docs/skills)
|
|
53
|
+
- [Antigravity workflow migration](https://antigravity.google/docs/migration/workflows-to-skills/)
|
|
54
|
+
- [Antigravity headless execution](https://antigravity.google/docs/cli/headless/)
|
|
55
|
+
- [pi skills](https://github.com/earendil-works/pi/blob/main/packages/coding-agent/docs/skills.md)
|
|
56
|
+
- [pi CLI](https://github.com/earendil-works/pi/blob/main/packages/coding-agent/docs/cli.md)
|
|
@@ -0,0 +1,70 @@
|
|
|
1
|
+
# Run checkpoint
|
|
2
|
+
|
|
3
|
+
Copy this structure into the project's `.si-overnight/<run-id>/run.md` and replace
|
|
4
|
+
the illustrative values with actual observations. Keep it compact and current;
|
|
5
|
+
use the user's language for the content. This is a checkpoint, not executable
|
|
6
|
+
instructions that override the user or current project rules.
|
|
7
|
+
|
|
8
|
+
```markdown
|
|
9
|
+
# Overnight run: <run-id>
|
|
10
|
+
|
|
11
|
+
## Contract
|
|
12
|
+
|
|
13
|
+
- Phase: intake | running | complete | stopped | blocked
|
|
14
|
+
- Project / working directory:
|
|
15
|
+
- Branch / worktree, if any:
|
|
16
|
+
- Started at (ISO 8601 with offset):
|
|
17
|
+
- Stop at (ISO 8601 with offset) / agreed duration:
|
|
18
|
+
- Mode: queue | discover
|
|
19
|
+
- Primary outcomes and acceptance criteria:
|
|
20
|
+
- Approved backup tasks (queue mode):
|
|
21
|
+
- Discovery areas and categories (discover mode):
|
|
22
|
+
- Excluded paths, behaviors, and decisions:
|
|
23
|
+
- Delivery and authorized actions:
|
|
24
|
+
- Known budget/cap; telemetry source, or unknown:
|
|
25
|
+
- Decisions from this run's interview:
|
|
26
|
+
- Still-unanswered questions and which tasks they affect:
|
|
27
|
+
|
|
28
|
+
## Baseline
|
|
29
|
+
|
|
30
|
+
- Existing user changes / ownership boundaries:
|
|
31
|
+
- Relevant project instructions:
|
|
32
|
+
- Available environment and missing access (names only, no secrets):
|
|
33
|
+
- Checks already failing before edits:
|
|
34
|
+
|
|
35
|
+
## Queue
|
|
36
|
+
|
|
37
|
+
| ID | Outcome / acceptance check | Status | Evidence / blocker |
|
|
38
|
+
| --- | --- | --- | --- |
|
|
39
|
+
| T1 | ... | pending | ... |
|
|
40
|
+
|
|
41
|
+
Use pending, doing, done, blocked, or unverified. In discover mode, append a
|
|
42
|
+
candidate only after recording its observed benefit and fit with the contract.
|
|
43
|
+
|
|
44
|
+
## Latest checkpoint
|
|
45
|
+
|
|
46
|
+
- Updated at:
|
|
47
|
+
- Current task and changed files:
|
|
48
|
+
- Last command, exit status, and relevant result:
|
|
49
|
+
- Work in progress / verification still needed:
|
|
50
|
+
- Repeated blocker and attempts so far:
|
|
51
|
+
- Next concrete action:
|
|
52
|
+
- Stop reason, if stopped:
|
|
53
|
+
|
|
54
|
+
## Verification evidence
|
|
55
|
+
|
|
56
|
+
| Task | Command and working directory | Outcome | Evidence or log path |
|
|
57
|
+
| --- | --- | --- | --- |
|
|
58
|
+
| T1 | ... | passed / failed / unavailable | ... |
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
For `report.md`, summarize completed outcomes, changed files, verification,
|
|
62
|
+
unfinished work, stop reason, and the next action. Do not copy enormous command
|
|
63
|
+
outputs or sensitive data into either file. Reference local logs when needed.
|
|
64
|
+
|
|
65
|
+
Example resume prompt, adapted to the current host's invocation syntax:
|
|
66
|
+
|
|
67
|
+
```text
|
|
68
|
+
Use si-overnight. Resume the run at .si-overnight/<run-id>/run.md.
|
|
69
|
+
Reconcile the checkpoint with the working tree first. Keep the agreed scope.
|
|
70
|
+
```
|