Skip to content
TrustedSkillsbeta
Back to all skills

1K Git Workflow

Listed
onekeyhq·vlatest·backend

Automates common Git workflows like branching, merging, and pull requests directly from your OneKeyHQ backend tasks.

Repository

Install on your platform

This skill no longer installs under the name 1k-git-workflow. onekeyhq/app-monorepo has no skill named "1k-git-workflow" any more. It was renamed, moved or deleted upstream.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-29. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

onekeyhq

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

Nobody has reviewed this code. TrustedSkills indexes and links skills; it does not audit, run or scan them. A skill runs with whatever access you give your agent — read the source before you install it.

Automated safety checks

scanned

We could not read this skill's source, so none of the checks below were run.

Not scanned. none of the 36 skills in the repository match this slug — it was most likely renamed or removed upstream after the registry indexed it Source recorded as onekeyhq/app-monorepo.
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

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.