Khemoo Version Control Pipeline FAQs

Question 1

What happens if a reviewer requests changes during the PR stage?

Accepted Answer

The skill will identify the specific issues flagged by the agents, assist you in committing the necessary fixes as new micro-units, and re-run the review cycle until approval is reached.

Question 2

Which AI agents participate in the code review process?

Accepted Answer

The skill dispatches core reviewers for logic, security, quality, performance, and testing. It can also trigger specialist agents for UI/UX, DevOps, or Documentation depending on the files changed.

Question 3

How does the skill determine the next version number?

Accepted Answer

It analyzes commit messages since the last tag. If it detects breaking changes, it suggests a Major bump; new features trigger a Minor bump; and bug fixes or refactors trigger a Patch.

Question 4

What is a micro-unit commit in Khemoo-VC?

Accepted Answer

A micro-unit commit is a commit that focuses on a single logical concern, such as a single fix or feature. This skill helps you split large changes into these smaller units to ensure a clean and revertible project history.

Question 5

Can I use specific parts of the workflow independently?

Accepted Answer

Yes, while the full pipeline is available via /khemoo-vc, you can use sub-commands like /khemoo-vc commit or /khemoo-vc release to target specific stages of the version control process.

Khemoo Version Control Pipeline

Key Features

Use Cases

Khemoo Version Control Pipeline

Key Features

Use Cases