菜单
Send feedback about this plugin repository as a GitHub issue. Use when the user says "feedback", "send feedback", "report issue", "bug report", "feature request", "フィードバック", "バグ報告", "機能リクエスト", or wants to create an issue for the plugin repository.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user asks to "lint AI assistant config", "check AGENTS.md", "validate SKILL.md", "agnix lint", or wants to detect and fix best-practice violations in Claude Code / agent configuration files.
This skill is the mandatory reference for all Claude Code hook creation. Use cc-hooks-ts for every hook. This skill should be used when the user asks to "create a hook", "add a hook", "write a hook", "implement a hook", "rewrite hooks in TypeScript", "use cc-hooks-ts", or needs to build any Claude Code hook — cc-hooks-ts is always required regardless of whether explicitly mentioned.
Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
This skill should be used when the user asks to "handoff from CCS", "Claude Codeの作業を引き継ぐ", "rate limit handoff", "context overflow", or wants to resume interrupted work from another CCS profile session.
This skill should be used when the user asks for "code review", "レビューして", "review this diff", "実装をレビュー", or wants rigorous review of recently created artifacts.
Direct utility reference for code-review PR scripts. Documents unresolved-thread, comment, CI-status, and CI-log helpers used by higher-level PR workflows.
| name | mutils:feedback |
| description | Send feedback about this plugin repository as a GitHub issue. Use when the user says "feedback", "send feedback", "report issue", "bug report", "feature request", "フィードバック", "バグ報告", "機能リクエスト", or wants to create an issue for the plugin repository. |
Create a GitHub issue on the masseater/codex-plugin repository based on the current conversation context.
Review the conversation history and identify what the user wants to report:
Present the draft to the user before creating. The draft must include:
Title: A concise, descriptive title in English
Labels: MUST include the claude label (triggers Claude Code Action for automated implementation). Additionally choose:
bug for bugsenhancement for feature requestsquestion for questionsBody (Markdown, in English):
## Context
[What the user was doing when the issue arose]
## Description
[Clear description of the issue or request]
## Steps to Reproduce (if bug)
1. [Step 1]
2. [Step 2]
## Expected Behavior (if bug)
[What should happen]
## Actual Behavior (if bug)
[What actually happens]
## Additional Context
- Plugin: [which plugin is affected]
- Relevant files: [file paths if applicable]
Use AskUserQuestion to confirm:
Run:
gh issue create \
--repo masseater/codex-plugin \
--title "<title>" \
--body "<body>" \
--label "claude" --label "<additional-label>"
Show the created issue URL to the user.