菜单
Commit message writing rules for Awesome Sirus Launcher. Use when Codex or another agent needs to describe a commit, prepare a commit message, summarize staged or unstaged changes for git, or propose a conventional commit after code, docs, build, changelog, rules, or skill changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Backend implementation rules for the Awesome Sirus Launcher Electron TypeScript backend. Use when editing TypeScript core modules, Electron main/preload adapters, IPC contracts, file downloads, MD5 client patch checks, WTF backups, FPS patch installation, GitHub addon installation, launcher auto-update, account profile storage, Config.wtf account switching, settings persistence, logging, or game launch behavior.
Changelog maintenance rules for Awesome Sirus Launcher. Use whenever Codex or another agent changes project files, adds features, fixes bugs, changes docs, modifies build/release behavior, updates agent rules, or prepares a versioned release so CHANGELOG.md and VERSION stay accurate.
Frontend implementation rules for the Awesome Sirus Launcher Vue renderer. Use when editing Vue components, Pinia stores, renderer routes, UI states, progress views, settings screens, addon management screens, backup screens, patch/update screens, logs, or user-facing error handling.
| name | commit |
| description | Commit message writing rules for Awesome Sirus Launcher. Use when Codex or another agent needs to describe a commit, prepare a commit message, summarize staged or unstaged changes for git, or propose a conventional commit after code, docs, build, changelog, rules, or skill changes. |
Use this skill when preparing a commit description. Base the message on actual changed files and behavior, not on the original user request alone.
git status --short.git diff or git diff --staged.Prefer Conventional Commits:
type(scope): short imperative summary
Optional body with concise details.
Allowed common types:
feat: new user-facing capability or planned capability.fix: bug fix.docs: documentation-only changes.build: build, packaging, release, CI, dependency tooling.test: tests only.refactor: behavior-preserving code restructure.chore: repository maintenance, rules, skills, metadata.ci: GitHub Actions and automation.Use scopes when helpful: docs, agents, backend, frontend, build, release, addons, patches.
docs, chore, or ci.CHANGELOG.md was updated because of the change, do not make the commit only about the changelog; describe the real change.docs: add launcher roadmap and agent rules
chore(agents): add changelog maintenance skill
ci: add version-gated build workflow
docs(addons): define GitHub source zip install flow