Release 1.1.3 — long skills keep their later steps

Fix release for 1.1.2: the 14 longest skills keep their later phases
after a compaction, a question nobody answered is never taken as an
answer, settings read the same from a subfolder, the commit check works
for a project in a subfolder of a larger repository, every skill opens
with a title, and the shipped allow rules no longer approve deleting a
branch or writing files without asking. Details in CHANGELOG.md; upgrade
steps in UPGRADING.md (v1.1.2 → v1.1.3).

Refs #83
Refs #133

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0185en4t76fPn7315q4c3nko
This commit is contained in:
Donchitos
2026-10-08 17:52:48 +11:00
co-authored by Claude Opus 5.5
parent b21fa0f7f2
commit be8993bbc5
231 changed files with 12000 additions and 10527 deletions
+2 -2
View File
@@ -75,8 +75,8 @@ A tier is the directory a spec lives in. The rubric category is the agent's
1. Read `catalog.yaml` to get the `spec:` path and `category:` — from the
`skills:` entry for a skill, the `agents:` entry for an agent
2. Read the skill at `.claude/skills/[name]/SKILL.md`, or the agent at
`.claude/agents/[name].md`
2. Read the skill at `.claude/skills/[name]/SKILL.md` and every file in its
`references/` folder, or the agent at `.claude/agents/[name].md`
3. Read the project `CLAUDE.md` and the files it imports with `@`: every
subagent receives them, so a rule stated there (for example a redirect in
`coordination-rules.md`) counts as the skill's or agent's own