How do I install the 1k Git Workflow skill?

Run npx skillmds add majiayu000/1k-git-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the 1k Git Workflow skill do?

Git workflow and conventions — branching, commit messages, and PR creation. It is listed under Productivity on SkillMD.

Is 1k Git Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 1k Git Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 1k Git Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published 1k Git Workflow?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

1k Git Workflow by majiayu000 — Agent Skill

Name: 1k Git Workflow
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

OneKey Git Usage Guidelines

Branch Management

Main branch: x - This is the primary development branch
Workflow: x → create feature branch → develop → PR back to x
Do not use onekey, master, or main as the base branch - always use x
NEVER work directly on the x branch → ALWAYS create feature branches

Branch Naming

Feature branches: feat/description or feature/description
Bug fixes: fix/description
Refactoring: refactor/description

Commit Message Format

Use Conventional Commits format:

feat: - New features
fix: - Bug fixes
refactor: - Code refactoring
perf: / optimize: - Performance improvements
chore: - Build, version, or non-code changes
docs: - Documentation only

Format: type: short description

Use lowercase
Keep first line under 72 characters
Include issue number if applicable: fix: resolve login bug OK-12345

IMPORTANT - Claude Code commits:

Do NOT include "Generated with Claude Code" link
Do NOT include "Co-Authored-By: Claude" signature
Commit message should be indistinguishable from human-written commits

PR Naming Convention

Follow the same format as commit messages:

feat: add dark mode support
fix: resolve authentication timeout issue
refactor: simplify payment processing logic

Common Git Commands

Creating a Feature Branch

git checkout x
git pull origin x
git checkout -b feat/my-new-feature

Committing Changes

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:

NEVER commit code that fails linting or TypeScript compilation
Pre-commit checks are mandatory as specified in CLAUDE.md
The /commit command handles this automatically

Pushing and Creating PR

git push -u origin feat/my-new-feature
# Then create PR via GitHub UI or gh CLI

Rebasing on Latest x

git fetch origin
git rebase origin/x

---name: 1k-git-workflowdescription: Git workflow and conventions — branching, commit messages, and PR creation.--- # OneKey Git Usage Guidelines ## Branch Management - **Main branch**: `x` - This is the primary development branch - **Workflow**: `x` → create feature branch → develop → PR back to `x` - Do not use `onekey`, `master`, or `main` as the base branch - always use `x` - **NEVER** work directly on the `x` branch → ALWAYS create feature branches ## Branch Naming - Feature branches: `feat/description` or `feature/description` - Bug fixes: `fix/description` - Refactoring: `refactor/description` ## Commit Message Format Use Conventional Commits format: - `feat:` - New features - `fix:` - Bug fixes - `refactor:` - Code refactoring - `perf:` / `optimize:` - Performance improvements - `chore:` - Build, version, or non-code changes - `docs:` - Documentation only **Format**: `type: short description` - Use lowercase - Keep first line under 72 characters - Include issue number if applicable: `fix: resolve login bug OK-12345` **IMPORTANT - Claude Code commits**: - Do NOT include "Generated with Claude Code" link - Do NOT include "Co-Authored-By: Claude" signature - Commit message should be indistinguishable from human-written commits ## PR Naming Convention Follow the same format as commit messages: - `feat: add dark mode support` - `fix: resolve authentication timeout issue` - `refactor: simplify payment processing logic` ## Common Git Commands ### Creating a Feature Branch ```bash git checkout x git pull origin x git checkout -b feat/my-new-feature ``` ### Committing Changes **Option 1: Use /commit command (Recommended)** ```bash /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** ```bash # 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**: - NEVER commit code that fails linting or TypeScript compilation - Pre-commit checks are mandatory as specified in CLAUDE.md - The `/commit` command handles this automatically ### Pushing and Creating PR ```bash git push -u origin feat/my-new-feature # Then create PR via GitHub UI or gh CLI ``` ### Rebasing on Latest x ```bash git fetch origin git rebase origin/x ```

Frequently asked questions