github-workflow-automation
Skill0 starsChanged 3 months agoMITView on GitHub
Automate Git commits, pull requests, releases, and CI/CD workflows. Apply automatically when the request matches; the user does not need to mention this skill.
- Reads credentials
- Commits and pushes
45 other projects use a version of this.
Adopted by
Most recently taken up by
- poizoncoded/skillstheir own version, first seen Nov 1, 2026
- OpenxIntelligence/Coding-Agent-Skillstheir own version, first seen Nov 1, 2026
- proffesor-for-testing/agentic-qetheir own version, first seen Oct 25, 2026
- I-Onlabs/claude-code-skillstheir own version, first seen Oct 25, 2026
- ruvnet/ruflotheir own version, first seen Oct 21, 2026
- karim-bhalwani/agent-skills-collectiontheir own version, first seen Oct 20, 2026
Used with
Projects with it also use V3 DDD Architecture, V3 Memory Unification and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ruvnetSkillV3 DDD Architecture
Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.
Also in 27 projects that use this
ruvnetSkillV3 Memory Unification
Unify 6+ memory systems into AgentDB with HNSW indexing for 150x-12,500x search improvements. Implements ADR-006 (Unified Memory Service) and ADR-009 (Hybrid Memory Backend).
Also in 27 projects that use this
nbossnSkillworker-benchmarks
Run comprehensive worker system benchmarks and performance analysis
Also in 9 projects that use this
ZekiogSkillagent-agent
Agent skill for agent - invoke with $agent-agent
Also in 5 projects that use this
ZekiogSkillagent-analyze-code-quality
Agent skill for analyze-code-quality - invoke with $agent-analyze-code-quality
Also in 5 projects that use this
- +3 more from ruvnet
- +4 more from Zekiog
Other versions45 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 45
- ruvnet/wifi-densepose★ 103ksame name
- ruvnet/RuView★ 103ksame name
- ruvnet/claude-flow★ 80ksame name
- ruvnet/ruflo★ 79ksame name
- ruvnet/ruvector★ 4.7ksame name
- ruvnet/RuVector★ 4.7ksame name
- ruvnet/agentic-flow★ 838same name
- proffesor-for-testing/agentic-qe★ 524same name
- FNOSP/FlyNarwhal★ 519same name
- FNOSP/fntv-client-multiplatform★ 519same name
35 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository76 other files it gives its agents.
- app-store-submission-packagerSkill
- digital-product-inventorSkill
- ios-testflight-github-actionsSkill
- meta-ads-analyzerSkill
- get-to-know-a-clientSkill
- investigate-before-recommendSkill
- production-system-auditSkill
- similarweb-analyticsSkill
- stock-analysisSkill
- system-architectSkill
- autonomous-github-syncSkill
- autonomous-sync-scriptSkill
- github-gem-seekerSkill
- organize-github-reposSkill
- using-git-worktreesSkill
- brainstorm-logosSkill
- brand-driven-ux-overhaulSkill
- canvas-designSkill
- excel-generatorSkill
- frontend-designSkill
- inspirational-music-video-productionSkill
- theme-factorySkill
- video-generatorSkill
- multiplayer-game-builderSkill
- promo-code-systemSkill
- realistic-ai-persona-builderSkill
- role-based-access-controlSkill
- serverless-debuggingSkill
- vertical-expansion-blueprintSkill
- manus-mcp-configuratorSkill
- mcp-auto-recoverySkill
- mcp-builderSkill
- mcp-connector-testerSkill
- mcp-ecosystem-optimizerSkill
- voice-ai-integrationSkill
- api-endpoint-builderSkill
- database-schema-generatorSkill
- testing-frameworkSkill
- deployment-automationSkill
- error-monitoring-setupSkill
- analytics-dashboardSkill
- email-system-builderSkill
- feature-flag-systemSkill
- user-authentication-systemSkill
- cron-job-schedulerSkill
- file-upload-systemSkill
- notification-systemSkill
- payment-integrationSkill
- search-implementationSkill
- debug-mining-engineSkill
- doc-coauthoringSkill
- docxSkill
- internet-skill-finderSkill
- pdfSkill
- pptxSkill
- project-handoff-ingestionSkill
- serverless-debuggingSkill
- skill-arsenal-builderSkill
- skill-creatorSkill
- skill-demo-builderSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 246
Use present tense ("Add feature" not "Added feature")
- Distinctive: line 257
Run tests on every push
- Distinctive: line 259
Use caching for dependencies
- Distinctive: line 264
Never commit secrets to repository
- Distinctive: line 407
Write commit message: 2 min
- Distinctive: line 410
Check CI/CD: 1 min
- Very specific: line 413
Run auto_commit.py: 30 sec
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
github-workflow-automation
Automate Git commits, pull requests, releases, and CI/CD workflows
Overview
Automate GitHub workflows including intelligent auto-commits, CI/CD pipelines, automated releases, and pull request management. Saves time on repetitive Git operations and ensures consistent workflow practices.
Time Saved: ~20 minutes per workflow setup
Complexity: Medium
Prerequisites: Git, GitHub CLI (gh), Node.js
When to Use
- Automating Git commits and pushes
- Setting up CI/CD pipelines
- Creating automated releases
- Managing pull requests programmatically
- Standardizing team workflows
Features
- Auto-Commit - Intelligent commit message generation and push
- CI/CD Templates - Ready-to-use GitHub Actions workflows
- Release Automation - Automated versioning and releases
- Workflow Patterns - Best practices and common patterns
Quick Start
1. Auto-Commit and Push
python3 /home/ubuntu/skills/github-workflow-automation/scripts/auto_commit.py /path/to/repo2. Auto-Commit with Custom Message
python3 /home/ubuntu/skills/github-workflow-automation/scripts/auto_commit.py /path/to/repo "Add new feature"3. Set Up CI/CD Workflow
# Copy template to project
cp /home/ubuntu/skills/github-workflow-automation/templates/ci-cd.yml /path/to/repo/.github/workflows/ci-cd.ymlHow It Works
Auto-Commit Script
Phase 1: Detection
- Checks for git repository
- Detects changed files
- Analyzes file types
Phase 2: Message Generation
- Generates intelligent commit message based on changes
- Or uses custom message if provided
Phase 3: Commit and Push
- Stages all changes (
git add .) - Commits with generated/custom message
- Pushes to current branch
Usage Examples
Example 1: Auto-Commit After Making Changes
# Made changes to multiple files
python3 /home/ubuntu/skills/github-workflow-automation/scripts/auto_commit.py ~/my-project
# Output:
# 📁 Repository: /home/ubuntu/my-project
# 📝 Changes detected:
# M src/index.js
# M src/styles.css
# 💬 Commit message: Update JavaScript/TypeScript code
# 📦 Staging changes...
# 💾 Committing...
# ✅ Committed successfully
# 🌿 Current branch: main
# 🚀 Pushing to origin/main...
# ✅ Pushed successfully!
# 🎉 All done!Example 2: Custom Commit Message
python3 /home/ubuntu/skills/github-workflow-automation/scripts/auto_commit.py ~/my-project "Fix critical bug in authentication"
# Output:
# 📁 Repository: /home/ubuntu/my-project
# 📝 Changes detected:
# M src/auth.js
# 💬 Commit message: Fix critical bug in authentication
# 📦 Staging changes...
# 💾 Committing...
# ✅ Committed successfully
# 🌿 Current branch: main
# 🚀 Pushing to origin/main...
# ✅ Pushed successfully!
# 🎉 All done!Example 3: Set Up CI/CD Pipeline
# Create workflows directory
mkdir -p ~/my-project/.github/workflows
# Copy CI/CD template
cp /home/ubuntu/skills/github-workflow-automation/templates/ci-cd.yml ~/my-project/.github/workflows/ci-cd.yml
# Commit and push
python3 /home/ubuntu/skills/github-workflow-automation/scripts/auto_commit.py ~/my-project "Add CI/CD workflow"Intelligent Commit Messages
The auto-commit script generates context-aware commit messages:
| File Types Changed | Generated Message |
| Only .md files | "Update documentation" |
| .py files | "Update Python code" |
| .js or .ts files | "Update JavaScript/TypeScript code" |
| .json files | "Update configuration" |
| .css or .scss files | "Update styles" |
| Single file | "Update {filename}" |
| Multiple files | "Update {count} files" |
CI/CD Workflow Template
Features
- ✅ Runs on push to main/develop
- ✅ Runs on pull requests
- ✅ Linting
- ✅ Testing
- ✅ Building
- ✅ Automatic deployment to production
Customization
Edit .github/workflows/ci-cd.yml:
# Change Node version
- uses: actions/setup-node@v3
with:
node-version: '20' # Change here
# Add environment variables
env:
DATABASE_URL: ${{ secrets.DATABASE_URL }}
API_KEY: ${{ secrets.API_KEY }}
# Customize deployment
- name: Deploy to production
run: |
npm run deploy # Your deploy commandRelease Workflow Template
Features
- ✅ Triggers on version tags (v*)
- ✅ Creates GitHub release
- ✅ Builds artifacts
- ✅ Uploads build to release
Usage
# Tag a release
git tag v1.0.0
git push --tags
# GitHub Actions will automatically:
# 1. Build the project
# 2. Create a release
# 3. Upload artifactsGitHub CLI Integration
Create Pull Request
gh pr create --title "Add new feature" --body "Description of changes"Merge Pull Request
gh pr merge <pr-number> --squashCreate Release
gh release create v1.0.0 --title "Version 1.0.0" --notes "Release notes"View Workflow Runs
gh run list
gh run view <run-id>Best Practices
1. Commit Messages
- Use present tense ("Add feature" not "Added feature")
- Be descriptive but concise
- Reference issues when applicable
2. Branch Strategy
main- Production-ready codedevelop- Development branchfeature/*- Feature brancheshotfix/*- Urgent fixes
3. CI/CD
- Run tests on every push
- Deploy only from main branch
- Use caching for dependencies
- Set up notifications
4. Secrets Management
- Store sensitive data in GitHub Secrets
- Never commit secrets to repository
- Use environment-specific secrets
5. Workflow Organization
- One workflow per purpose
- Use descriptive names
- Document workflow purpose
- Keep workflows DRY
Troubleshooting
Auto-Commit Fails
Problem: "Not a git repository"
# Solution: Initialize git
cd /path/to/project
git init
git remote add origin <url>Problem: "Failed to push"
# Solution: Pull first
git pull origin main --rebase
# Then run auto-commit againWorkflow Not Running
Problem: Workflow file not detected
# Solution: Check file location
# Must be in .github/workflows/
# File must have .yml or .yaml extensionProblem: Workflow syntax error
# Solution: Validate YAML
# Use GitHub Actions validator or yamllintPermission Denied
Problem: "Permission denied" when pushing
# Solution: Check authentication
gh auth status
gh auth loginAdvanced Usage
Conditional Workflows
# Only run on specific paths
on:
push:
paths:
- 'src/**'
- '!**/*.md'Matrix Testing
strategy:
matrix:
node-version: [16, 18, 20]
os: [ubuntu-latest, windows-latest]Reusable Workflows
# .github/workflows/reusable.yml
on:
workflow_call:
inputs:
environment:
required: true
type: stringFiles
Scripts
scripts/auto_commit.py- Intelligent auto-commit and push
Templates
templates/ci-cd.yml- Complete CI/CD pipelinetemplates/release.yml- Automated release workflow
References
references/workflow_patterns.md- Patterns and best practices
Related Skills
- deployment-automation - Deploy after CI/CD passes
- error-monitoring-setup - Monitor deployed applications
- testing-framework - Generate tests for CI/CD
Workflow
1. User makes changes to code
2. User runs auto_commit.py
3. Script detects changes and generates message
4. Script commits and pushes
5. GitHub Actions triggers CI/CD
6. Tests run automatically
7. If tests pass, deploy to productionSuccess Criteria
✅ Changes committed automatically
✅ Intelligent commit messages generated
✅ CI/CD pipeline runs on push
✅ Tests execute successfully
✅ Deployment automated
Time Savings
Manual Git Workflow: ~5 minutes per commit
- Check status: 30 sec
- Stage files: 30 sec
- Write commit message: 2 min
- Commit: 30 sec
- Push: 30 sec
- Check CI/CD: 1 min
With This Skill: ~30 seconds
- Run auto_commit.py: 30 sec
Savings: ~4.5 minutes per commit
Daily Savings (10 commits): ~45 minutes
Future Enhancements
- Conventional commits support
- Automatic changelog generation
- Semantic versioning automation
- PR template generation
- Code review automation
- Merge conflict resolution
- Branch protection rules setup
Created: February 10, 2026
Status: Production Ready
Tested: GitHub, GitHub Actions, GitHub CLI
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

