Git Commit with Database Sync

VerifiedSafe

Commits changes from the `content/` directory without requiring knowledge of the monorepo structure. It includes a pre-commit hook that runs a session review to catch stale task references. Use this skill when you need to make safe, focused commits to content files only.

Sby Skills Guide Bot
DevelopmentBeginner
706/2/2026
Claude Code
#git#commit#content-management#monorepo

Recommended for

Our review

Commits changes from the content/ directory in a monorepo, with a pre-commit check for stale task references.

Strengths

  • Simplifies committing for users unfamiliar with the monorepo structure
  • Integrates an automatic check via the session-review skill
  • Restricts commits to the content/ directory, reducing errors
  • Provides a dry-run mode to preview changes without committing

Limitations

  • Does not push changes to the remote repository
  • Only works for the content/ directory
  • Requires the session-review skill to also be set up
When to use it

Use this skill to commit changes in the content/ directory of a monorepo, especially if you are not comfortable with the full repository structure.

When not to use it

Avoid using it if you need to commit files outside content/ or if you need to push changes immediately to remote.

Security analysis

Safe
Quality score85/100

The skill runs a controlled bash script that only stages and commits from a specific 'content/' directory. No destructive or exfiltrating commands are used. The allowed tools are limited to the commit script and git, and the pre-commit check uses an internal session-review skill, posing no risk.

No concerns found

Examples

Commit all content changes
Commit all changes in the content directory with the message 'Updated diary entry'.
Commit a specific file
Commit the file diary/2026/01/17-Sat.md with message 'Added new entry'.
Dry run commit
Show what would be committed without actually committing.

name: commit description: Git commit workflow with database sync. allowed-tools: Bash(.claude/skills/commit/scripts/commit.sh:), Bash(git:)

Commit Skill

Commit changes from the content directory without needing to know about the monorepo structure.

Pre-commit Check

Before committing, run the session review skill to catch stale task references:

  • Use /session-review or follow .claude/skills/session-review/SKILL.md
  • Fix any flagged mismatches before proceeding with the commit

Usage

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

# Commit specific files
.claude/skills/commit/scripts/commit.sh "Your commit message" diary/2026/01/17-Sat.md

# Show what would be committed (dry run)
.claude/skills/commit/scripts/commit.sh --dry-run "Message"

What It Does

  1. Changes to the repository root (parent of content/)
  2. Stages only files within content/
  3. Creates a commit with the provided message
  4. Returns status

Notes

  • Only commits files in the content/ directory
  • Does not push to remote
  • Safe to use without understanding the full repo structure
Related skills