1K Git Workflow

What it does

This skill automates common Git workflows within a OneKeyHQ backend environment. It enforces specific branching strategies, naming conventions for branches and commits, and provides tools to streamline commit creation while ensuring code quality through pre-commit checks. The skill guides users in creating feature branches, committing changes with a standardized format, and adhering to established pull request naming conventions.

When to use it

• When developing new features within the OneKeyHQ x branch environment.
• To ensure consistent commit message formatting across your team.
• When needing to quickly create and manage feature branches for development tasks.

Key capabilities

• Enforces a specific branching workflow using the x main branch.
• Provides guidelines for naming feature branches, bug fixes, and refactoring efforts.
• Mandates Conventional Commits format for commit messages (e.g., feat:, fix:, refactor:).
• Offers a /commit command to automate pre-commit checks (yarn lint:staged and yarn tsc:staged) and create formatted commits.
• Prevents the inclusion of "Generated with Claude Code" links or "Co-Authored-By: Claude" signatures in commit messages.

Example prompts

• /commit (to initiate a pre-checked commit)
• "Create a feature branch for adding user profile page." (implicitly guides creation of feat/user-profile-page)
• "What is the correct format for a bug fix commit message?"

Tips & gotchas

• Always base new branches off of the x branch – avoid using onekey, master, or main.
• Ensure your code passes both yarn lint:staged and yarn tsc:staged checks before committing manually.
• The /commit command is the recommended method for creating commits to ensure adherence to formatting standards.