Automate per-repo commits and pushes across the fyli monorepo.
npx skills add https://github.com/Kibbey/fyli --skill commit-kibbey
Please help me install this Agent Skill. Skill: commit Source: https://github.com/Kibbey/fyli/tree/main/.claude/skills/commit Command: npx skills add https://github.com/Kibbey/fyli --skill commit-kibbey
This Skill automates the process of committing and pushing changes across all repositories in the fyli monorepo. It detects changes per sub-repo, stages only relevant files, and constructs conventional commit messages for consistent history.
Run the commit workflow to scan for changes, stage files per repo, generate Conventional Commits, and push to origin.
High-intent search queries and answers about installing and using this skill.
To automate git commits across a monorepo, this Skill detects changes in each sub-repo, stages relevant files individually, generates conventional commit messages, and pushes each repository independently to avoid cross-repo conflicts.
The best way to prevent cross-repo conflicts is performing safe per-repo pushes. The Skill handles per-repo changes independently, staging and pushing each repository separately to avoid accidental cross-repo conflicts or invalid branch pushes.
You generate conventional commit messages automatically by running this workflow. It performs per-repo analysis on detected changes and constructs standardized conventional commit messages to maintain a consistent history across the monorepo.
Yes, you can use bash git commands to stage and commit files safely. The Skill uses Bash commands to orchestrate staging, ensuring only relevant files are committed per sub-repo before executing safe independent pushes to origin.
Yes, this monorepo commit automation works with specific sub-repos like cimplur-core and fyli-fe-v2. It explicitly handles changes, staging, and messaging for these sub-repos along with fyli-infra and the root repository.
Automated monorepo pushes fail on non-existent branches due to unsafe cross-repo pushing. This Skill prevents such failures by analyzing each repository individually and performing safe per-repo pushes to avoid accidental pushes to non-existent branches.
4IRLAnalyze local Git branch changes and generate a markdown report.
levkissManage GitHub repositories via GitHub CLI for commits, branches, pull requests, issues, releases, and Pages deployment.
Tony363Automate Git operations with Conventional Commits and MCP integrations.
mhattingpeteStage, commit, and push code changes with conventional commit messages.
