菜单
Use when the user asks to generate, update, or refresh project documentation, CLAUDE.md, context files, or scoped rules. Creates Claude-optimized documentation with a short CLAUDE.md (<200 lines), detailed docs/CONTEXT.md, and path-scoped rules.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user asks to analyze, audit, review, or check code quality across the project. Performs full codebase analysis — detects bad patterns, security flaws, performance issues, misconfigurations — and generates a prioritized report in docs/ANALYSIS-{date}.md.
Use when the user asks to analyze, document, inspect, or understand the database schema. Connects to the live database (Docker or direct) and reads ORM code to produce comprehensive docs/DB.md with tables, relations, indexes, and query patterns.
Use when the user wants to set up, create, inspect, or manage PolyForge nocturnal routines — the banked embers that keep the forge working after hours. Subcommands: "embers light" installs/configures nightly routines, "embers cast" creates a custom routine, "embers watch" inspects logs/telemetry, "embers tend" lists/suspends/resumes/deletes/runs them.
Use when the user asks to clean up, squash, reorganize, or rewrite commit history on the current branch before a PR. Groups messy commits into logical, reviewable units while preserving meaningful history.
Use when the user asks to review a PR, check a pull request, review a GitHub issue, review a Jira ticket, look at changes before merge, or audit code quality. Auto-detects the item type (PR, GitHub issue, Jira ticket) and adapts the review accordingly.
Use when the user asks to initialize, set up, or configure PolyForge for a project, or when starting work on a project with no .claude/polyforge.json. Scans the project, detects stack and architecture, and generates optimized configuration interactively.
| name | engrave |
| description | Use when the user asks to generate, update, or refresh project documentation, CLAUDE.md, context files, or scoped rules. Creates Claude-optimized documentation with a short CLAUDE.md (<200 lines), detailed docs/CONTEXT.md, and path-scoped rules. |
You are PolyForge's documentation generator. Create documentation optimized for Claude Code.
/engrave Generate all documentation
/engrave --claude-md Only update CLAUDE.md
/engrave --context Only update docs/CONTEXT.md
/engrave --rules Only update .claude/rules/
CLAUDE.md — under 200 lines strict. Every line must pass: "Would removing this cause Claude to make mistakes?" If no, cut it.docs/CONTEXT.md — detailed architecture, dependencies, data flow, key patterns, quirks. No size limit..claude/rules/ — scoped rule files with paths: frontmatter.Spawn [model: sonnet] subagent to scan and return structured JSON only:
{ "stack": {}, "entryPoints": [], "architecture": "", "patterns": [], "conventions": [], "envVars": [], "knownQuirks": [], "keyFiles": [], "testFrameworks": [] }
Subagent reads: entry points, config files, main modules, existing docs. Discard raw scan data — use only the JSON.
AskUserQuestion with options: "Merge" / "Keep + create separate" / "Replace (backup to tmp/)" / "Other"Show preview with file names and line counts. Then call AskUserQuestion — "Generate these files?" with options: "Generate all" / "Preview one file" / "Cancel" / "Other". See @skills/shared/common-patterns.md § "User Questions — AskUserQuestion ONLY".
Generate each file from structured summary. Compact between files.
CLAUDE.md — only: build/test/lint commands, architecture, non-obvious conventions, @ refs to detailed docs. Include PolyForge commands list.
.claude/rules/ — scope with paths: frontmatter. Positive assertions, one per line.
Update lastUpdatedAt in .claude/polyforge.json. Compact after final file.