format-and-commit

Format code comments and create conventional commits for PR preparation.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/datamktkorea/agent-skills --skill format-and-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: format-and-commit
Source: https://github.com/datamktkorea/agent-skills/tree/main/plugins/dmk-oneteam/skills/format-and-commit
Command: npx skills add https://github.com/datamktkorea/agent-skills --skill format-and-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dmk-oneteam:format-code-comments, dmk-oneteam:git-commit, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of formatting code comments and creating commits, saving time and reducing errors in the PR preparation workflow.

Core Features & Use Cases

  • Sequential Execution: Combines code-comment formatting and commit creation into one streamlined workflow.
  • User Approval: Ensures user confirmation at each stage before committing changes.
  • Safety: Never runs 'git add .', 'git add -A', or 'git commit -a', maintaining staging discipline.
  • Use Case: A developer uses this skill to format code comments and prepare a commit for a pull request, ensuring all changes are ready before submission.

Quick Start

Use the format-and-commit skill to prepare a commit after formatting your code comments.

Frequently Asked Questions about format-and-commit

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

FAQPage Schema
How do I automate code formatting and conventional commits before a pull request?

To automate code formatting and conventional commits before a pull request, this skill sequentially formats code comments and then creates a commit, streamlining PR preparation into a single workflow while ensuring user approval at each stage.

Can I use this to format code comments and create a git commit in one step?

Yes, you can format code comments and create a git commit in one step. The skill coordinates two dependent operations to format comments first, then generate a conventional commit, reducing manual errors in your workflow.

Does the commit automation run git add automatically for all modified files?

No, the commit automation does not run git add automatically for all files. It maintains strict staging discipline by never executing 'git add .', 'git add -A', or 'git commit -a', ensuring you keep full control over staged changes.

What is the safest way to prepare conventional commits for PR submission?

The safest way to prepare conventional commits for PR submission is using an automated workflow that requires explicit user confirmation before applying changes. This approach prevents accidental file staging and maintains code quality without 'git add -A' commands.

Why do I need to approve changes during the commit automation workflow?

You need to approve changes during the commit automation workflow to ensure safety and accuracy. The skill pauses for user confirmation at each stage before formatting comments and creating the final commit, preventing unintended modifications.