You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ef9808f
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .claude/skills/project-structure/SKILL.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ includes the tests) and `vitest.config.ts`.
29
29
| Server | Layout | Where its features are registered |
30
30
| --- | --- | --- |
31
31
|`everything`|`index.ts` picks a transport from `argv`; `server/` holds the factory; `tools/`, `resources/`, `prompts/` hold one file per feature plus an `index.ts`; `transports/` holds one file per transport; `version.ts` reads the package version; `docs/` is shipped | Each feature file exports a `register…` function, wired into its area's `index.ts` (`registerTools`, `registerResources`, `registerPrompts`), which `server/index.ts` calls from `createServer()`|
32
-
|`filesystem`|`index.ts` is the stdio entry point (argv → allowed directories, `main()`); `server.ts` exports `createServer(allowedDirectories)`; `lib.ts` holds the file operations and path validation, with the allow-list passed in rather than held globally; `path-utils.ts`, `path-validation.ts` and `roots-utils.ts` are focused helpers; `version.ts` reads the package version | Inline in `createServer()` in `server.ts`, with `server.registerTool(...)`|
32
+
|`filesystem`|`index.ts` is the stdio entry point (argv → allowed directories, `main()`); `server.ts` exports `createServer(allowedDirectories)`; `lib.ts` holds the file operations and path validation, with the allow-list passed in rather than held globally; `path-utils.ts`, `path-validation.ts` and `roots-utils.ts` are focused helpers, and `pinned-directory.ts` runs the write operations inside their verified directory; `version.ts` reads the package version | Inline in `createServer()` in `server.ts`, with `server.registerTool(...)`|
33
33
|`memory`|`index.ts` holds the `KnowledgeGraphManager`, `createServer(memoryFilePath)` and the stdio `main()`; `version.ts` reads the package version | Inline in `createServer()`; the resource and its subscription handlers are exported `register…` functions in the same file |
34
34
|`sequentialthinking`|`index.ts` holds `createServer()` and the stdio `main()`; `lib.ts` holds `SequentialThinkingServer`, the logic; `version.ts` reads the package version | Inline in `createServer()`|
Copy file name to clipboardExpand all lines: .claude/skills/security-advisory/SKILL.md
+67Lines changed: 67 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -257,6 +257,52 @@ before anyone merges it.
257
257
the advisory, so this card is the only place the rest of the team can see the
258
258
work exists at all.
259
259
260
+
#### Work the fix leaves open: a follow-up card
261
+
262
+
A fix can leave part of the problem open: a platform the fix cannot reach yet,
263
+
or a residual exposure that needs a larger change. That work cannot become a
264
+
public issue before publication either, because describing it describes the
265
+
vulnerability. Track it with a **second draft card**, the advisory's
266
+
**follow-up card**, rather than widening the fix or leaving the gap in a PR
267
+
body nobody will read again.
268
+
269
+
-**Title:**`[GHSA-xxxx-yyyy-zzzz follow-up]`, as opaque as the advisory's
270
+
own card. The `[GHSA-` prefix keeps it inside the board audit's advisory
271
+
exemption. The advisory card's lookup (`/board-ops`) matches
272
+
`[GHSA-xxxx-yyyy-zzzz]` with its closing bracket, so it never finds the
273
+
follow-up by mistake. A second follow-up for the same advisory is
274
+
`[GHSA-xxxx-yyyy-zzzz follow-up 2]`.
275
+
-**Body:** the same link-and-triage-only rule as step 1. Its lines, in order:
276
+
-`**Advisory:** <html_url>` on the first line.
277
+
-`Follow-up to the fix for this advisory. Convert to an issue only once the advisory is published.`
278
+
- A link to the write-up.
279
+
- The `Priority <level> (provisional, <YYYY-MM-DD>)` line.
280
+
-**The write-up lives in the private fork**, where only the advisory's
281
+
collaborators can read it. Draft it as the public issue it will become
282
+
(problem, options, acceptance criteria), and post it as a `COMMENT` review on
283
+
the fork's PR, since the fork refuses issue comments (see the API table).
284
+
-**Status `Todo`** when a maintainer asked for the follow-up: the advisory is
285
+
already accepted, and asking for the work approves it. Otherwise it goes in
286
+
`Incoming`. Score its Priority with step 1's table, using the severity of the
287
+
residual exposure rather than the advisory's.
288
+
-**Say in the fix PR's body what the fix leaves open**, and link the
289
+
follow-up. The advisory's text must say it too when it is published (step 5).
290
+
291
+
Create it with `/board-ops`'s draft-card recipe, using the follow-up title in
292
+
place of `[$GHSA]`.
293
+
294
+
⚠️ **The follow-up card is the only exception beyond the advisory's own
295
+
card.** Any other untracked work an advisory's review turns up falls into one
296
+
of three cases:
297
+
298
+
- It is part of the fix.
299
+
- It is a **separate vulnerability**, which goes through its own private
300
+
advisory: this repository's for ours, or the SDK's advisory form for an
301
+
SDK's (step 2). Publishing this advisory never makes another one safe to
302
+
disclose.
303
+
- It is non-security work outside the advisory's scope, which gets a public
304
+
issue **after publication**, like any other finding.
305
+
260
306
### 5. Merge, release, publish (human only)
261
307
262
308
Publish **after** the fix has shipped in a release, never before: publishing
@@ -296,6 +342,12 @@ advisory is what users and advisory tooling (Dependabot, `npm audit`,
296
342
added, and an unadded finder is simply never credited.
297
343
-**A CVE**, if one is wanted: optional, and the advisory is the only place to
298
344
request one.
345
+
-**What the fix leaves open**, if the advisory has a follow-up card. Say which
346
+
platforms or cases are still exposed, so a user who upgrades does not believe
347
+
they are fully covered.
348
+
-**The follow-up's write-up, copied out of the fork** before publishing. Once
349
+
the advisory is published, don't count on the temporary fork, or on access to
350
+
it, surviving.
299
351
300
352
### 6. After publication, convert the card into public tracking
301
353
@@ -322,6 +374,20 @@ issues and two cards.
322
374
**close** the issue: the work shipped before the issue existed.
323
375
5. Move the card to **`Done`**, which is right here because the fix shipped.
324
376
377
+
**A follow-up card converts at the same time, but stays open**, because its
378
+
work has not shipped:
379
+
380
+
1. Retitle it `[GHSA-xxxx-yyyy-zzzz follow-up] - <summary>`.
381
+
2. Convert it.
382
+
3. Replace the body's triage lines with the write-up copied out of the fork
383
+
(step 5), linking the now-public advisory.
384
+
4. Apply `/issue-create`'s labels. A card already past `Incoming` also takes
385
+
the milestone the follow-up is planned for, not the one the fix shipped in.
386
+
A card still in `Incoming` stays unmilestoned: once it is an issue the
387
+
ordinary `Incoming` ⇔ no-milestone rule applies, and a maintainer approves
388
+
it by assigning the milestone and moving it to `Todo`.
389
+
5. Leave the issue open, and leave the card in the Status it had.
390
+
325
391
## API facts worth not re-deriving
326
392
327
393
| Thing | Fact |
@@ -333,6 +399,7 @@ issues and two cards.
333
399
| Fork idempotency | Read `.private_fork` first; the POST creates, it does not probe |
334
400
| Fork deletion | Needs the `delete_repo` OAuth scope, which a default `gh` token lacks |
335
401
| Comments |**No API at all**, REST or GraphQL; UI-only |
402
+
| Fork PR comments | Issue comments (`gh pr comment`, `issues/N/comments`) are refused and `…/comments/{id}/replies` returns `404`; reply in a thread with `POST pulls/N/comments -F in_reply_to=<id>`, and post a PR-level summary as a `COMMENT` review |
336
403
| Credits |`credits_detailed` on the advisory; a private report carries the reporter's credit (`type``reporter`, `state``pending` or `accepted`) from submission |
337
404
| Board writes | Not automatable from Actions: `GITHUB_TOKEN` cannot hold `organization projects: write`|
338
405
| SDK routing | Both SDK repos have private vulnerability reporting enabled; use their advisory forms |
Copy file name to clipboardExpand all lines: .claude/skills/security-advisory/evals/evals.json
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -30,5 +30,9 @@
30
30
{
31
31
"prompt": "Rename the local variable `tmp` to `buffer` in this snippet: `const tmp = 1; return tmp + 1;`",
32
32
"expect": null
33
+
},
34
+
{
35
+
"prompt": "The fix for a private advisory only covers Linux and macOS; Windows needs a bigger change. Where do I track the Windows work before the advisory is published?",
0 commit comments