القائمة
This skill should be used when the user asks to "organize commits", "split this diff into commits", "コミットを整理", "レビューしやすいコミット", or wants current changes grouped into logical commits.
التثبيت باستخدام 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 | code-review:organize-commits |
| description | This skill should be used when the user asks to "organize commits", "split this diff into commits", "コミットを整理", "レビューしやすいコミット", or wants current changes grouped into logical commits. |
現在のブランチの変更内容を分析し、レビュアーが理解しやすいように関心ごと単位で論理的なコミットに整理してください。
git statusで変更ファイル一覧を取得git diffで未ステージの変更を確認git diff --stagedでステージ済みの変更を確認git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/@@'
git remote show origin | grep 'HEAD branch' | awk '{print $NF}'で確認以下の観点で変更をグループ化：
📊 変更内容の分析結果
━━━━━━━━━━━━━━━━━━━━━━━━━━━
合計: X ファイル変更
🎯 推奨コミット構成:
[1] feat: [機能の説明]
影響ファイル:
- src/components/NewFeature.tsx
- src/hooks/useNewFeature.ts
[2] fix: [バグ修正の説明]
影響ファイル:
- src/utils/calculation.ts
[3] refactor: [リファクタリング内容]
影響ファイル:
- src/components/OldComponent.tsx
[4] chore: [その他の変更]
影響ファイル:
- package.json
- tsconfig.json
━━━━━━━━━━━━━━━━━━━━━━━━━━━
ユーザーに以下を確認：
承認後、以下の手順で実行：
git resetgit add [files]<type>(<scope>): <subject>
<body>
<footer>
Type:
git log --oneline [デフォルトブランチ]..HEADでデフォルトブランチからの差分コミットを表示git diff [デフォルトブランチ]...HEAD --statで変更ファイルの統計を確認$ARGUMENTS