菜单
Drafts conventional commit messages and pull request bodies for marchat without committing or pushing unless explicitly requested. Use when the user asks for a commit message, PR description, or git workflow help; also read at the end of every substantive implementation task.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Implements marchat terminal client TUI, commands, keystore, and WebSocket client behavior. Use when editing client/, Bubble Tea models, :commands, themes, notifications, or client configuration paths.
Implements marchat server hub, WebSocket handlers, admin web, health, and startup validation. Use when editing server/, cmd/server/, hub routing, admin panel, or server configuration.
Writes and runs marchat tests with race detection, coverage, and dialect smoke patterns. Use when adding tests, fixing test failures, measuring coverage, or when the user mentions go test, -race, TESTING.md, or CI database smoke.
Changes marchat SQL schema and queries across SQLite, PostgreSQL, and MySQL using dialect helpers. Use when editing server/db.go, db_dialect.go, schema migrations, MARCHAT_DB_PATH, or multi-database behavior.
Implements and refactors marchat Go code with project toolchain and quality gates. Use when adding features, fixing bugs, touching client/server/plugin code, or when the user asks to develop, build, or validate marchat changes.
Develops and maintains marchat plugins: SDK, host IPC, manager install path, store downloads, and Ed25519 licenses. Use when editing plugin/, plugin commands, or plugin_state.json behavior.
| name | git-workflow-marchat |
| description | Drafts conventional commit messages and pull request bodies for marchat without committing or pushing unless explicitly requested. Use when the user asks for a commit message, PR description, or git workflow help; also read at the end of every substantive implementation task. |
git commit or git push unless the user explicitly asks.git status, git diff), including prior uncommitted work from earlier turns in the same session.Conventional commits: feat:, fix:, chore:, docs:, style:, ci:, test:.
<type>(<optional scope>): <short summary>
<optional body: why, not a file list>
Examples:
fix(server): use dialect boolean literals in pin toggle SQL
Postgres rejected integer comparison on boolean columns.
docs: refresh TESTING coverage from merged profile
git status, git diff, git log -1 --oneline (style reference)..env, keys).git status.Use gh when user asks to create a PR:
git log main...HEAD, git diff main...HEAD.-u only if needed and user asked.gh pr create with Summary and Test plan sections.Note in commit body and CHANGELOG.md when protocol or keystore format breaks compatibility.