skills.rest
glhewett
glhewettCOMMUNITY
Explore all skills by this author →
Website𝕏@greg_hewettGitHub

git-commit-non-code

Create git commits for non-code file changes with CI skip annotations.

Updated Feb 15, 2026
Search Tags:#git#documentation#commit#push#non-code#ci-skip
One-click install
npx skills add https://github.com/glhewett/public-skills --skill git-commit-non-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-non-code
Source: https://github.com/glhewett/public-skills/tree/main/git-commit-non-code
Command: npx skills add https://github.com/glhewett/public-skills --skill git-commit-non-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps maintain consistent, safe git commits for non-code changes (documentation, configuration, and other repository metadata) so those edits are recorded properly, annotated for CI behavior, and optionally published to the remote.

Core Features & Use Cases

  • Structured commit creation: Ensures relevant non-code files are staged and committed with a clear message.
  • CI annotation support: Reminds or includes CI-skip comments when required by project CI providers.
  • Optional push behavior: Allows pushing the commit to the remote when requested.
  • Use Case: Updating README or config files and creating a commit that skips CI to avoid unnecessary pipeline runs while preserving a clear history.

Quick Start

Create a git commit for the current non-code documentation and configuration changes, include any CI-skip comments, and push to the remote if the push-commit option is true.

Frequently Asked Questions about git-commit-non-code

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

FAQPage Schema
How do I commit non-code files like documentation and skip CI pipeline runs?▼

To commit non-code files and skip CI, stage the documentation or configuration changes and include a CI-skip annotation in the commit message. This prevents unnecessary pipeline runs while preserving a clear repository history.

What is the best way to track configuration file updates in git without triggering deployments?▼

Tracking configuration file updates without triggering deployments involves staging the non-code modifications and adding CI-skip comments to the commit message, optionally pushing the commit to the remote repository if requested.

Can I push documentation changes to a remote repository while skipping continuous integration?▼

Yes, you can push documentation changes while skipping continuous integration by staging the files, committing them with a CI-skip flag in the message, and optionally pushing the commit to the remote repository.

When do I need to add CI skip annotations to a git commit?▼

You need CI skip annotations when committing non-code changes like README or config files to avoid unnecessary pipeline executions. This ensures edits are recorded properly and annotated for CI behavior without wasting build resources.

How do I stage and commit repository metadata changes separately from code?▼

Stage and commit repository metadata changes separately by selectively adding the non-code files to the git index, writing a clear commit message, and including CI-skip annotations to prevent automated pipeline triggers.

Related Skills

Explore More Software Engineering Skills→
borkwebborkweb
7

commit-writer

Generate conventional git commit messages from staged diffs and repository history.

Community
Intermediate
antonyfmunozantonyfmunoz

git

Manage Git version control tasks for EOS code with commit, branch, merge, and push workflows.

Community
Intermediate
tanglgtanglg

setup-pre-commit

Automate installation and configuration of pre-commit hooks for Git repositories.

Community
Intermediate
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic