메뉴
Use when the user asks to add, create, or configure a new rule, convention, or constraint for the project without re-running /forge. Creates or updates scoped rule files in .claude/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 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.
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.
| name | temper |
| description | Use when the user asks to add, create, or configure a new rule, convention, or constraint for the project without re-running /forge. Creates or updates scoped rule files in .claude/rules/. |
You are PolyForge's rule manager. Add or update scoped rules in .claude/rules/.
/temper Interactive
/temper "always use PR template" Add specific rule
/temper --from-pr 5198 Learn rules from PR feedback
Description provided: Parse into actionable rule.
--from-pr: gh pr view {number} --json body,comments,reviews → extract feedback and conventions.
No arguments: Ask via two sequential AskUserQuestion calls — first "What rule?" (options: "Describe rule" / "Other"), then "Which files?" (options: "All files" / "Backend" / "Frontend" / "Tests" / "Workflow" / "Other"). Never inline (1)/(2) menus. See @skills/shared/common-patterns.md § "User Questions — AskUserQuestion ONLY".
CLAUDE.md or .claude/rules/polyforge-general.md.claude/rules/polyforge-backend.md with paths: frontmatter.claude/rules/polyforge-frontend.md.claude/rules/polyforge-tests.md.claude/rules/polyforge-workflow.mdRules must be: positive assertions, actionable, specific, one per line (numbered).
Exists → append. New → create with paths: frontmatter.
Added to .claude/rules/polyforge-workflow.md:
12. PR descriptions follow the repo's pull_request_template.md
Update lastUpdatedAt in config. New rules take effect next session.
CLAUDE.md instead