commits:restructure

Converts non-conventional commit messages into conventional commit formats.

5|3|Updated May 19, 2026
One-click install
npx skills add https://github.com/awinogradov/code-assistants --skill commits-restructure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commits:restructure
Source: https://github.com/awinogradov/code-assistants/tree/main/claude-plugins/autopilot/skills/commits%3Arestructure
Command: npx skills add https://github.com/awinogradov/code-assistants --skill commits-restructure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the issue of messy, non-conventional commit messages, helping maintain a clean and standardized commit history.

Core Features & Use Cases

  • Commit Restructuring: Converts non-standard commit messages into conventional commit formats.
  • Base Branch Comparison: Compares current branch against a specified base branch.
  • Error Handling: Ensures clean working directory and base branch existence before proceeding.

Quick Start

Run the 'commits:restructure' skill with the optional base branch argument: skill commits:restructure --base <branch>

Frequently Asked Questions about commits:restructure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert non-conventional git commits into a standard format?

The commits:restructure skill transforms messy draft commit messages into conventional commit formats. It ensures a standardized commit history by comparing your current branch against a specified base branch.

How do I restructure commit messages against a specific base branch?

Run the skill using `skill commits:restructure --base <branch>`. This targets the specified base branch for comparison, identifying commits that deviate from conventional commit message standards and restructuring them accordingly.

What happens if my working directory is not clean during commit restructuring?

The commit restructuring process includes error handling that requires a clean working directory and an existing base branch. If these prerequisites are not met, the operation will stop to prevent corrupting repository maintenance efforts.

When do I need to use conventional commit formats for repository maintenance?

Conventional commit formats are needed for repository maintenance when teams enforce strict commit message standards. Restructuring draft commits into this format ensures a consistent and readable repository history for all contributors.

Does commit restructuring work without specifying a base branch?

The skill requires a base branch argument to compare against your current branch. Running `skill commits:restructure --base <branch>` is necessary to isolate the draft commits that require conversion into conventional commit formats.