commit-docs

Commit documentation and configuration files with a [skip-cd] tag.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/har1101/marp-agent-har1101 --skill commit-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-docs
Source: https://github.com/har1101/marp-agent-har1101/tree/main/.claude/skills/commit-docs
Command: npx skills add https://github.com/har1101/marp-agent-har1101 --skill commit-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unnecessary and time-consuming deployments to Amplify by automatically identifying and committing changes that do not affect the application's runtime or build process.

Core Features & Use Cases

  • Selective Committing: Commits only documentation, configuration, and non-code related files.
  • Deployment Skipping: Appends [skip-cd] to commit messages, leveraging Amplify Hosting's feature to bypass builds and deployments.
  • Use Case: After updating the project's README or adjusting .gitignore files, use this skill to commit these changes without triggering a full application deployment, saving time and resources.

Quick Start

Commit documentation changes with the default message by running /commit-docs.

Frequently Asked Questions about commit-docs

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

FAQPage Schema
How do I skip Amplify deployments for documentation changes?

To skip Amplify deployments for documentation changes, commit non-code files with a [skip-cd] tag in the commit message. This targets directories like docs/ and root Markdown files to bypass the build process entirely.

What is the [skip-cd] tag used for in AWS Amplify?

The [skip-cd] tag in AWS Amplify is used to bypass builds and deployments. Appending it to a commit message prevents Amplify Hosting from triggering unnecessary application deployments for non-runtime changes.

Which files can I commit without triggering an Amplify build?

You can commit files within docs/, .claude/, .github/, .vscode/, root Markdown files, and .gitignore without triggering an Amplify build. Changes to critical source code directories are flagged for deployment.

Does committing .gitignore changes trigger a full application deployment?

Committing .gitignore changes does not trigger a full application deployment when using a selective commit tool. These configuration files are appended with [skip-cd] to prevent unnecessary Amplify builds.

When should I not use the skip-cd deployment bypass?

You should not use the skip-cd deployment bypass when modifying critical source code directories. Changes affecting the application's runtime or build process must deploy normally to update the live environment.