菜单
PLACEHOLDER — do not invoke. This folder exists only so `apm install` has something to resolve during workshop setup. Your real skill belongs in a NEW folder under .apm/skills/<your-skill>/, generated by your harness from a Genesis design. See docs/tracks/.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when the user asks to migrate, upgrade, or modernize a Node.js codebase from Express 4 to Express 5 — including phrasings like "bump express to v5", "upgrade express", "migrate to express 5", "express deprecation warnings", "we're stuck on express 4", or when preparing a major-version dependency PR involving express ^4.x. Also fires when the user mentions removed Express APIs (app.del, res.send(status), the deprecated body-parser bundling), discontinued path-to-regexp 0.x patterns (e.g. unnamed wildcards `*` or optional segments `:id?`), or asks for a migration plan / breaking changes audit on an Express 4 repo. This skill audits, classifies (SAFE / AUTOFIX / MANUAL), applies safe autofixes, and emits a phased migration plan grounded in the official Express 5 migration guide. It does NOT run the consumer's tests; it emits a plan the team executes.
Use this skill to drive a pull request from review to green CI. It composes the review-panel as its per-PR review primitive, folds non-blocking findings as commits, pushes, and watches CI to green. Activate when a PR needs end-to-end review-and-fix before merge. This is the advanced driver skill from the Agentic SDLC track.
Use this skill to run a multi-persona expert advisory review on a labelled pull request against zava-storefront. The panel fans out to three specialist reviewers (correctness, security, test-coverage), each running in its own agent thread, plus a synthesizer that arbitrates and renders ONE recommendation comment. Activate when a PR is labelled `panel-review` or when a non-trivial PR needs a cross-cutting recommendation before merge.
| name | my-skill |
| description | PLACEHOLDER — do not invoke. This folder exists only so `apm install` has something to resolve during workshop setup. Your real skill belongs in a NEW folder under .apm/skills/<your-skill>/, generated by your harness from a Genesis design. See docs/tracks/. |
| license | UNLICENSED |
| allowed-tools | [] |
🚫 Don't fill this file in. It's a marker, not a skeleton.
apm install needs a real folder under .apm/skills/ to bootstrap the
workshop. That's it. The skill you ship in this workshop is a new
folder you'll create — .apm/skills/test-improver/, .apm/skills/docs-generator/,
etc. You will not edit this file.
The workshop's hardest lesson: don't open a text editor and start typing SKILL.md while squinting at Genesis's prose output. That's how every "failed to ship" skill is born. The discipline is:
Design with Genesis. In your harness, run /genesis with your
chosen track's prompt. Genesis returns an
ASCII architecture diagram + an interface spec. Read it. That's
your contract.
Generate the skill from the design. Paste Genesis's design back into chat, then instruct your harness:
Generate the <your-skill> skill at
.apm/skills/<your-skill>/following the Genesis design above. Use the SKILL.md frontmatter conventions from.github/instructions/prose-style.md(installed byapm installfromcode-kit).
Your harness writes SKILL.md (and any references) into the new
folder. You review the output, you don't author it line-by-line.
Iterate on the design, not the implementation. Don't like the output? Tweak the Genesis prompt (narrow the inputs, add a constraint), regenerate, re-ask the harness to regenerate the skill. The implementation is a function of the design — keep the design sharp and the implementation follows.
In a real codebase you will redesign skills as your team's conventions evolve. If the implementation is hand-typed, every redesign is a rewrite-from-scratch. If the implementation is generated from a persisted design, every redesign is one Genesis tweak + one regenerate prompt. That's the loop you're learning here.
See your chosen track guide for the exact Genesis prompt + the reference ASCII diagram you should expect to get back.
