commit

Commit content/ directory changes in a monorepo using a Bash script.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/vogon101/KnowledgeWork --skill commit-vogon101
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/vogon101/KnowledgeWork/tree/main/skills/commit
Command: npx skills add https://github.com/vogon101/KnowledgeWork --skill commit-vogon101

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates committing changes from the content/ directory within a monorepo, eliminating manual steps and ensuring consistent commit hygiene.

Core Features & Use Cases

  • Stage only files under content/ for commits.
  • Create a new commit with a provided message.
  • Dry-run option to preview what would be committed without making changes.

Quick Start

Commit all content changes with a message: .claude/skills/commit/scripts/commit.sh "Your commit message"

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commits for a specific directory in a monorepo?

You can automate git commits for a specific directory in a monorepo by running a Bash script that stages changes exclusively under content/ and creates a commit. This isolates content updates without staging unrelated files.

Can I preview monorepo content changes before making a git commit?

Yes, you can preview monorepo content changes before a git commit by passing the --dry-run option to the script. This previews staged files without modifying the repository state.

Does this automated commit script push changes to a remote repository?

No, the automated commit script does not push to a remote repository. It stages files in the content/ directory and creates a local git commit, requiring manual pushing afterwards.

How do I commit individual files instead of all content changes in a monorepo?

To commit individual files instead of all content changes in a monorepo, the script supports passing specific file paths alongside your commit message. This stages only the specified files rather than the entire content/ directory.

What are the limitations of using a Bash script for monorepo content commits?

Limitations of using a Bash script for monorepo content commits include dependency on standard git availability and lack of integrated remote pushing. It is scoped specifically to the content/ directory and requires a valid commit message argument.