Git Workflow FAQs

Question 1

What does the Git Workflow skill do?

Accepted Answer

The Git Workflow skill centralizes and automates standardized git operations within Claude Code. It handles branch creation using kebab-case naming, enforces atomic commits following Conventional Commits standards, and automates pull request generation with Linear issue linking.

Question 2

Does it support custom project conventions?

Accepted Answer

Yes. The skill reads conventions directly from your project's .env file. You can customize commit formats, branch prefixes for features, bugs, or chores, and define your specific GitHub organization and Linear team keys.

Question 3

What capabilities does the Git Workflow skill provide?

Accepted Answer

Key capabilities include validating working directory cleanliness, creating feature branches with standardized prefixes, formatting commits (conventional or simple) based on .env configurations, and delegating complex PR creation tasks to the /pr command for full context integration.

Question 4

When should I use this skill?

Accepted Answer

You should use this skill for all git-related operations during your development cycle. It is designed to be the single source of truth for git commands, ensuring that every change made by Claude Code adheres to your project's specific conventions and naming patterns.

Question 5

How does this skill improve my AI-assisted workflow?

Accepted Answer

It improves your workflow by eliminating manual git management and ensuring 100% repository consistency. By automating the 'Implementation -> Commit -> PR' loop, it maintains a clean project history and ensures every commit is traceable back to a specific Linear issue.

Git Workflow

Git Workflow

主な機能

ユースケース

主な機能

ユースケース