Fetching from the wire…
Public story · 2026-07-23 · high
Fork skills chained to their own output now run before that output exists, unless they opt out.
Why now: This shipped July 22 as Claude Code's follow-up to 2.1.215, which had already stopped /verify and /code-review from firing on their own.
Claude Code made background execution the default for /code-review and any skill declaring context: fork, per the 2.1.218 release notes posted July 22. That default flip matters most for anyone who built a multi-step skill assuming a fork step blocks until it returns a result. It doesn't anymore. The next step in the chain now fires immediately, before the forked skill's output exists. A skill opts back into the old behavior by setting background: false.
This pairs with 2.1.215, which stopped /verify and /code-review from firing automatically. That release put invocation back in your hands. Running them now costs no main-thread context, since output moves to a background subagent instead of the main conversation.
The failure mode is quiet. A chained skill that reads its own fork step's output will run against nothing, or against a stale result. The error that follows will look unrelated to the frontmatter flag that caused it.
Anyone maintaining custom skills should grep their files for context: fork and check what fires right after. The declaration's meaning changed on July 22, without a rename.
Each link below shares sources, entities, or timing with this story.
Same source
Cite the same source (anthropics/claude-code — Release v2.1.218).
Same source domain / Semantically similar
Reported by the same outlet (github.com); covers closely related ground (similarity 0.67).
Reported by the same outlet (github.com); covers closely related ground (similarity 0.60).
Semantically similar
Covers closely related ground (similarity 0.77).
Same source domain
Reported by the same outlet (github.com).
Reported by the same outlet (github.com).
Reported by the same outlet (github.com).
Reported by the same outlet (github.com).