@erclx/aitk 0.35.0 → 0.35.1

package/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "aitk",
   "description": "Automated governance, versioning, and discovery tools for Claude Code.",
-  "version": "0.35.0",
+  "version": "0.35.1",
   "author": {
     "name": "Eric Le",
     "url": "https://github.com/erclx"

package/claude/skills/bash-script/SKILL.md

@@ -9,6 +9,10 @@ Generate production-ready Bash scripts for DevOps and CLI workflows. Enforce str
 
 Load `${CLAUDE_SKILL_DIR}/references/patterns.md` for the timeline lifecycle, logging, interactive prompt, help-screen, and full-script code templates. `${CLAUDE_SKILL_DIR}` expands to this skill's own directory, so the path resolves from any project. Copy those definitions verbatim, keeping only the colors and functions the script actually uses.
 
+## Guards
+
+- A request for a script with no human at the terminal stops and routes to `cli-script`. CI jobs, cron entries, agent-run tasks, and any script whose output is consumed by a pipe render no timeline, so generating one costs the frame and returns nothing.
+
 ## Script setup
 
 - Start with `#!/usr/bin/env bash`, `set -e`, and `set -o pipefail`.

package/claude/skills/ci-workflow/SKILL.md

@@ -7,6 +7,11 @@ description: Generates GitHub Actions CI workflow files with parallel jobs, emoj
 
 Generate GitHub Actions workflow files for CI pipelines. Enforce parallel job execution, emoji job naming, and gated deployment stages.
 
+## Guards
+
+- A request for what runs inside a deploy, publish, or release job stops at the gate. Credentials, environments, and deploy targets are invisible to this skill, so emit the job with its `needs` wiring and a placeholder step, then name what the caller fills in. Never guess a deploy command.
+- The build, test, and deploy commands belong to the project. Read them from its scripts rather than asserting a second copy in the workflow.
+
 ## Workflow setup
 
 - Include `workflow_dispatch` on every workflow alongside the primary trigger.
@@ -49,4 +54,5 @@ Before responding, verify:
 - E2E uses `needs: build`. Release and deploy use `needs: e2e`.
 - Artifacts upload on `if: failure()` only with `retention-days: 7`.
 - Job names use emoji + title format.
+- Deploy, publish, and release jobs carry a placeholder step and a named handoff, never a guessed deploy command.
 - Bun projects use `oven-sh/setup-bun@v2` with `bun install --frozen-lockfile`.

package/claude/skills/docs-sync/SKILL.md

@@ -55,14 +55,19 @@ Read each discovered file in parallel.
 For each discovered doc, classify as one of:
 
 - `stale`: the diff touches something the doc describes
+- `departed`: the doc records a deliberate contract and the diff broke it
 - `unrelated`: no overlap between diff and doc content
 
+The split between `stale` and `departed` is whether the doc was describing or promising. A doc that trailed the code is `stale`. A doc stating a contract the code was meant to keep is `departed`, and rewriting it to match the diff would record the regression as the contract.
+
 Classify at the section level, not the file level. A doc edited earlier in the session can still be partially stale. For each diff surface, verify the corresponding section is synced.
 
 ## Action
 
 Rewrite only the stale sections. Do not touch sections unrelated to the diff. Write the updated file immediately after the preview. Claude Code's tool permission dialog is the confirmation gate. Do not wait for user input.
 
+Never rewrite a `departed` section. Leave it as written and report it as a finding, since the repair belongs in the code rather than in the prose.
+
 ## Response format
 
 ### Preview
@@ -73,6 +78,7 @@ Rewrite only the stale sections. Do not touch sections unrelated to the diff. Wr
 | Doc         | Status    | Action |
 | ----------- | --------- | ------ |
 | README.md   | stale     | update |
+| docs/cli.md | departed  | report |
 | docs/api.md | unrelated | skip   |
 
 After outputting the preview, write all stale updates immediately.
@@ -84,4 +90,5 @@ One line per file, using the same relative path format as the preview table (e.g
 ```plaintext
 ✅ Updated: <relative-path>
 ⏭️  Skipped: <relative-path>
+⚠️ Departed: <relative-path> records <the contract>, and the diff <what it did>. Left unwritten.
 ```

package/claude/skills/migration-claude-md/SKILL.md

@@ -7,6 +7,8 @@ description: Classifies each section of a target project's bloated `CLAUDE.md` i
 
 Rebalance a large `CLAUDE.md` so only always-load behavior stays in it, path-scoped behavior becomes a rule, and domain narrative becomes a context entry. Every move is a proposal the user applies by hand.
 
+Run `migration-context` first when both apply. Its moves populate `.claude/context/`, and Step 3 has to read the folder those moves left so an existing entry resolves to an append rather than blocking the move that should have created it.
+
 ## Guards
 
 - If no `CLAUDE.md` exists at `pwd`, stop: `❌ No CLAUDE.md found at the project root.`

package/claude/skills/migration-context/SKILL.md

@@ -5,6 +5,8 @@ description: Classifies markdown files in a target project's `docs/` folder and
 
 # Claude context migrate
 
+Run this skill before `migration-claude-md` when both apply. That skill proposes entries into the same `.claude/context/` folder, and an entry landing there first makes the corresponding move here read as a conflict and get skipped, which loses the richer `docs/` file.
+
 ## Guards
 
 - If no `docs/` directory exists at `pwd`, stop: `❌ No docs/ directory found.`

package/claude/skills/setup-gov/SKILL.md

@@ -36,13 +36,14 @@ Match the detected evidence to the catalog:
 
 If a detected technology has no matching rule, stop and surface the gap. Do not guess.
 
-Present three options:
+Present four options:
 
-1. Author a new rule in the toolkit at `governance/rules/<domain>/<num>-<name>.md` following `.claude/standards/rule.md`, or `${CLAUDE_SKILL_DIR}/../../standards/rule.md` when the project does not have it, commit, then re-run install.
-2. Install the matching non-<tech> rules and skip the tech-specific layer.
-3. Abort.
+1. Author a new rule in the toolkit at `governance/rules/<domain>/<num>-<name>.md` following `.claude/standards/rule.md`, or `${CLAUDE_SKILL_DIR}/../../standards/rule.md` when the project does not have it, commit, then re-run install. Take this route when the toolkit should ship the rule to every project.
+2. Invoke `create-rule`, which scaffolds the file into the target project at a non-colliding number. Take this route when the rule is specific to this project and no sync should ever overwrite it.
+3. Install the matching non-<tech> rules and skip the tech-specific layer.
+4. Abort.
 
-Rules are authored in the toolkit repository, never in the target project on the fly.
+This skill authors no rule itself. Option 1 writes in the toolkit repository, and option 2 hands the project-local file to `create-rule`.
 
 ## Preview
 

package/claude/skills/setup-init/SKILL.md

@@ -10,6 +10,7 @@ Orchestrates the onboarding chain. Detects project type, resolves per-domain arg
 ## Scope
 
 - This skill and `aitk init` run once on a fresh scaffold, never on an existing project. They do not guard against clobbering existing configs. When tempted to add guards, mode switches, or an existing-project branch, stop. Extend the per-domain `aitk <domain> install` or `aitk sync` paths instead.
+- The chain does not bootstrap the `index.md` system and does not provision Claude Code plugins. `setup-indexes` owns the first. `setup-plugins` owns the second, which installs once per machine rather than into a project, so no project-scoped chain can carry it. Name both in the report so a clean result does not read as onboarding complete.
 
 ## Read catalogs
 
@@ -112,3 +113,4 @@ After the chain, report:
 - `setup-verify` outcome
 - Any domains or scripts that failed
 - Any detection gaps surfaced during resolve
+- Onboarding steps left to the caller: `setup-indexes` for the `index.md` system, `setup-plugins` for Claude Code plugins

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/aitk",
   "type": "module",
-  "version": "0.35.0",
+  "version": "0.35.1",
   "description": "Infrastructure and quality tooling for developer workflows",
   "license": "MIT",
   "bin": {