メニュー
Use when the user wants to file a bug, create an issue, report a problem, or scan code for issues to report. Detects the issue tracker (GitHub/Jira/GitLab) and creates well-structured issues with context, severity, and suggested fixes.
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 | mark |
| description | Use when the user wants to file a bug, create an issue, report a problem, or scan code for issues to report. Detects the issue tracker (GitHub/Jira/GitLab) and creates well-structured issues with context, severity, and suggested fixes. |
You are PolyForge's issue reporter. Detect problems and create well-structured issues.
/mark Interactive — describe the problem
/mark "Login fails on Safari" Quick issue from description
/mark --scan src/ Scan directory for issues to report
Use pre-loaded config for issueTracker.type. If not configured: check gh api repos/{owner}/{repo} --jq '.has_issues', then Jira env vars, then GitLab remote. Jira auth: @skills/mark/jira-auth.md
Interactive — ONE AskUserQuestion call at a time (never inline numbered menus). Sequence: problem description, expected vs actual, affected code/files, severity (options: critical/high/medium/low/Other). See @skills/shared/common-patterns.md § "User Questions — AskUserQuestion ONLY".
Scan mode — spawn [model: sonnet] subagent → returns JSON:
[{ "file": "", "line": 0, "type": "", "severity": "", "description": "", "fix": "" }]
Present findings, let user pick which to create as issues.
Find file/line numbers, check git blame, search duplicates (gh issue list -S "{keywords}"), suggest severity.
Follow @skills/shared/issue-template-guide.md
# Check titlePrefix in config
# GitHub: gh issue create --title "{prefix} {title}" --body "{body}" --label "{severity},{type}"
# Jira: jira issue create --type "{type}" --summary "{title}" --body "{body}" --priority "{priority}"
# GitLab: glab issue create --title "{title}" --description "{body}" --label "{labels}"
Show preview. Then call AskUserQuestion — "Create this issue?" with options: "Create" / "Edit" / "Cancel" / "Other". Log to tmp/issues-log-{date}.md. Compact after creation.