Menü
Git workflow and conventions — branching, commit messages, and PR creation.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Analytics event tracking for OneKey. Use when adding tracking events, logging to server, user behavior tracking, or business metrics. Covers the @LogToServer decorator pattern, logger scope/scene architecture, and common pitfalls. Triggers on "埋点", "统计", "打点", "数据追踪", "日志", "analytics", "tracking event", "Mixpanel", "LogToServer", "trackEvent", "defaultLogger".
Create test versions to verify app auto-update functionality and version migration.
Release branch management — checkout from release, prepare builds, pre-release diff checks, publish tracking, and sync back to x. Use this skill when managing release branches, creating branches for bundle releases, running pre-release diff checks, finalizing releases, or syncing release changes to x. Triggers on "bundle release", "release diff", "release publish", "release sync", "release checkout", "发布管理", "release 分支", "release management", "bundle-release", "bundle branch".
Code quality standards — lint (eslint/oxlint), type check (tsc), pre-commit hooks, and comment conventions. All comments must be in English.
Comprehensive PR code review for OneKey monorepo. Use when reviewing PRs, code changes, or diffs — covers security (secrets/PII leakage, supply-chain, AuthN/AuthZ), code quality (hooks, race conditions, null safety, concurrent requests), and OneKey-specific patterns (Fabric crashes, MIUI, BigNumber). Triggers on "review PR", "review this PR", "code review", "check this diff", "审查 PR", "代码审查", "review
Coding patterns and best practices — React components, promise handling, and TypeScript conventions.
| name | 1k-git-workflow |
| description | Git workflow and conventions — branching, commit messages, and PR creation. |
| allowed-tools | Bash, Read |
x - This is the primary development branchx → create feature branch → develop → PR back to xonekey, master, or main as the base branch - always use xx branch → ALWAYS create feature branchesfeat/description or feature/descriptionfix/descriptionrefactor/descriptionUse Conventional Commits format:
feat: - New featuresfix: - Bug fixesrefactor: - Code refactoringperf: / optimize: - Performance improvementschore: - Build, version, or non-code changesdocs: - Documentation onlyFormat: type: short description
fix: resolve login bug OK-12345IMPORTANT - Claude Code commits:
Follow the same format as commit messages:
feat: add dark mode supportfix: resolve authentication timeout issuerefactor: simplify payment processing logicgit checkout x
git pull origin x
git checkout -b feat/my-new-feature
Option 1: Use /commit command (Recommended)
/commit
The /commit command automatically runs pre-commit checks (yarn lint:staged and yarn tsc:staged) and creates a well-formatted commit message.
Option 2: Manual commit with pre-checks
# Stage your changes
git add .
# Run pre-commit checks (MANDATORY)
yarn lint:staged
yarn tsc:staged
# If checks pass, commit
git commit -m "feat: add user profile page"
IMPORTANT:
/commit command handles this automaticallygit push -u origin feat/my-new-feature
# Then create PR via GitHub UI or gh CLI
git fetch origin
git rebase origin/x