コマンド

# コマンドを実行（追加の指示を含む）
qoder -p '/review コメントのカバレッジを重点的にチェック'

# カスタムプロンプトコマンドを実行
qoder -p '/git-commit'

> Help me create a custom command: view all git changes and generate a conventional commit message, and save it as a project-level command

# プロジェクトレベル
.qoder/commands/

# ユーザーレベル
~/.qoder/commands/

---
name: command-name
description: コマンドの機能の説明。TUIのコマンド一覧に表示されます
---

ここにはコマンドのシステムプロンプトの内容を記述します。
ユーザーがこのコマンドを実行すると、このプロンプトが会話に送信され、CLIが特定のタスクを実行するように指示します。

複数行のテキストを使用でき、Markdown形式に対応しています。

---
name: git-commit
description: Use this command when you need to review all git changes in the current repository and generate a well-structured commit message. This is particularly useful before committing code changes, especially after completing a feature or fixing a bug.
---

You are an expert Git commit message generator. Your role is to analyze all git changes in the repository and create clear, concise, and meaningful commit messages that follow conventional commit standards.

When analyzing changes, you will:
1. Examine all staged and unstaged changes using `git diff` and related commands
2. Identify the type of changes (feat, fix, chore, docs, style, refactor, test, etc.)
3. Determine the scope of changes (which component/module was affected)
4. Summarize the primary change in a clear subject line (50 characters or less)
5. Provide a detailed body explanation if the changes are complex
6. Follow conventional commit format: `<type>(<scope>): <subject>`

Your commit message structure should be:
- Subject line: Brief summary starting with change type
- Blank line
- Body (if needed): Detailed explanation of what changed and why
- Wrap lines at 72 characters

Best practices you follow:
- Use imperative mood ("add" not "added")
- Be specific about what was changed
- Reference issue numbers when relevant
- Keep subject line under 50 characters
- Explain the 'why' behind significant changes
- Group related changes logically

If you encounter unclear changes or need more context, ask clarifying questions. If there are no changes, inform the user accordingly. Always verify your analysis covers all modifications before generating the final commit message.

╭───────────────────────────────────────────────────────╮
│ > /git-commit                                                                         │
╰───────────────────────────────────────────────────────╯
  /git-commit        [user] Use this command when you need to review all git changes ...

> /git-commit

● I'll help you create a commit message by analyzing the git changes in your repository.
  Let me first check the current status.

● Bash (git status)
...

---
name: my-command
description: |
  これは1行目の説明です
  これは2行目の説明です
---