"\\ud83d\\udd27 GitHub Workflow Automation workflow skill. Use this skill when the user needs Patterns for automating GitHub workflows with AI assistance, inspired by Gemini CLI and modern DevOps practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off."
Instrucciones de origen · Vista previa de solo lectura
name
github-workflow-automation-v2
description
\ud83d\udd27 GitHub Workflow Automation workflow skill. Use this skill when the user needs Patterns for automating GitHub workflows with AI assistance, inspired by Gemini CLI and modern DevOps practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills/skills/github-workflow-automation from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
🔧 GitHub Workflow Automation > Patterns for automating GitHub workflows with AI assistance, inspired by Gemini CLI and modern DevOps practices.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: 1. Automated PR Review, ✅ What looks good, ⚠️ Potential Issues, 💡 Suggestions, 🔒 Security Notes, 2. Issue Triage Automation.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
Automating PR reviews with AI
Setting up issue triage automation
Creating GitHub Actions workflows
Integrating AI into CI/CD pipelines
Automating Git operations (rebases, cherry-picks)
Use when the request clearly matches the imported source intent: Patterns for automating GitHub workflows with AI assistance, inspired by Gemini CLI and modern DevOps practices.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.
# AI Review Structure## Examples### Example 1: Ask for the upstream workflow directly```text
Use @github-workflow-automation-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
```**Explanation:** This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
### Example 2: Ask for a provenance-grounded review```text
Review @github-workflow-automation-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
```**Explanation:** Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
### Example 3: Narrow the copied support files before execution```text
Use @github-workflow-automation-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
```**Explanation:** This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
### Example 4: Build a reviewer packet```text
Review @github-workflow-automation-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.
```**Explanation:** This is useful when the PR is waiting for human review and you want a repeatable audit packet.
### Imported Usage Notes#### Imported: Available Commands
| Command | Description |
| :------------------- | :-------------------------- |
| `@ai-helper explain` | Explain the code in this PR |
| `@ai-helper review` | Request AI code review |
| `@ai-helper fix` | Suggest fixes for issues |
| `@ai-helper test` | Generate test cases |
| `@ai-helper docs` | Generate documentation |
| `/rebase` | Rebase PR onto main |
| `/update` | Update PR branch from main |
| `/approve` | Mark as approved by bot |
| `/label bug` | Add 'bug' label |
| `/assign @user` | Assign to user |
```
---
## Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
- [ ] Store API keys in GitHub Secrets
- [ ] Use minimal permissions in workflows
- [ ] Validate all inputs
- [ ] Don't expose sensitive data in logs
- [ ] Cache dependencies
- [ ] Use matrix builds for parallel testing
- [ ] Skip unnecessary jobs with path filters
### Imported Operating Notes
#### Imported: Best Practices
### Security
- [ ] Store API keys in GitHub Secrets
- [ ] Use minimal permissions in workflows
- [ ] Validate all inputs
- [ ] Don't expose sensitive data in logs
### Performance
- [ ] Cache dependencies
- [ ] Use matrix builds for parallel testing
- [ ] Skip unnecessary jobs with path filters
- [ ] Use self-hosted runners for heavy workloads
### Reliability
- [ ] Add timeouts to jobs
- [ ] Handle rate limits gracefully
- [ ] Implement retry logic
- [ ] Have rollback procedures
---
## Troubleshooting
### Problem: The operator skipped the imported context and answered too generically
**Symptoms:** The result ignores the upstream workflow in `plugins/antigravity-awesome-skills/skills/github-workflow-automation`, fails to mention provenance, or does not use any copied source files at all.
**Solution:** Re-open `metadata.json`, `ORIGIN.md`, and the most relevant copied upstream files. Check the `external_source` block first, then restate the provenance before continuing.
### Problem: The imported workflow feels incomplete during review
**Symptoms:** Reviewers can see the generated `SKILL.md`, but they cannot quickly tell which references, examples, or scripts matter for the current task.
**Solution:** Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
### Problem: The task drifted into a different specialization
**Symptoms:** The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
**Solution:** Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
## Related Skills
- `@00-andruia-consultant` - Use when the work is better handled by that native specialization after this imported skill establishes context.
- `@00-andruia-consultant-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context.
- `@10-andruia-skill-smith` - Use when the work is better handled by that native specialization after this imported skill establishes context.
- `@10-andruia-skill-smith-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context.
## Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
| Resource family | What it gives the reviewer | Example path |
| --- | --- | --- |
| `references` | copied reference notes, guides, or background material from upstream | `references/n/a` |
| `examples` | worked examples or reusable prompts copied from upstream | `examples/n/a` |
| `scripts` | upstream helper scripts that change execution or validation | `scripts/n/a` |
| `agents` | routing or delegation notes that are genuinely part of the imported package | `agents/n/a` |
| `assets` | supporting assets or schemas copied from the source package | `assets/n/a` |
### Imported Reference Notes
#### Imported: Resources
- [Gemini CLI GitHub Action](https://github.com/google-github-actions/run-gemini-cli)
- [GitHub Actions Documentation](https://docs.github.com/en/actions)
- [GitHub REST API](https://docs.github.com/en/rest)
- [CODEOWNERS Syntax](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)
#### Imported: ✅ What looks good
- Well-structured code
- Good test coverage
- Clear naming conventions
#### Imported: ⚠️ Potential Issues
1. **Line 42**: Possible null pointer exception
```javascript
// Current
user.profile.name;
// Suggested
user?.profile?.name ?? "Unknown";
```
Line 78: Consider error handling
// Add try-catch or .catch()
Imported: 💡 Suggestions
Consider extracting the validation logic into a separate function
Add JSDoc comments for public methods
Imported: 🔒 Security Notes
No sensitive data exposure detected
API key handling looks correct
### 1.3 Focused Reviews
```yaml
# Review only specific file types
- name: Filter code files
run: |
files=$(git diff --name-only origin/${{ github.base_ref }}...HEAD | \
grep -E '\.(ts|tsx|js|jsx|py|go)$' || true)
echo "code_files=$files" >> $GITHUB_OUTPUT
# Review with context
- name: AI Review with context
run: |
# Include relevant context files
context=""
for file in ${{ steps.changed.outputs.files }}; do
if [[ -f "$file" ]]; then
context+="=== $file ===\n$(cat $file)\n\n"
fi
done
# Send to AI with full file context
# .github/workflows/stale.ymlname:ManageStaleIssueson:schedule:-cron:"0 0 * * *"# Dailyjobs:stale:runs-on:ubuntu-lateststeps:-uses:actions/stale@v9with:stale-issue-message:|
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed in 14 days if no further activity occurs.
If this issue is still relevant:-Addacommentwithanupdate-Removethe`stale`labelThankyouforyourcontributions!🙏stale-pr-message:|
This PR has been automatically marked as stale. Please update it or it
will be closed in 14 days.
days-before-stale:60days-before-close:14stale-issue-label:"stale"stale-pr-label:"stale"exempt-issue-labels:"pinned,security,in-progress"exempt-pr-labels:"pinned,security"
Imported: 3. CI/CD Integration
3.1 Smart Test Selection
# .github/workflows/smart-tests.ymlname:SmartTestSelectionon:pull_request:jobs:analyze:runs-on:ubuntu-latestoutputs:test_suites:${{steps.analyze.outputs.suites}}steps:-uses:actions/checkout@v4with:fetch-depth:0-name:Analyzechangesid:analyzerun:|
# Get changed files
changed=$(git diff --name-only origin/${{ github.base_ref }}...HEAD)
# Determine which test suites to runsuites="[]"ifecho"$changed"|grep-q"^src/api/";thensuites=$(echo$suites|jq'. + ["api"]')fiifecho"$changed"|grep-q"^src/frontend/";thensuites=$(echo$suites|jq'. + ["frontend"]')fiifecho"$changed"|grep-q"^src/database/";thensuites=$(echo$suites|jq'. + ["database", "api"]')fi# If nothing specific, run allif [ "$suites"="[]" ];thensuites='["all"]'fiecho"suites=$suites">>$GITHUB_OUTPUTtest:needs:analyzeruns-on:ubuntu-lateststrategy:matrix:suite:${{fromJson(needs.analyze.outputs.test_suites)}}steps:-uses:actions/checkout@v4-name:Runtestsrun:|
if [ "${{ matrix.suite }}" = "all" ]; then
npm test
else
npm test -- --suite ${{ matrix.suite }}
fi
3.2 Deployment with AI Validation
# .github/workflows/deploy.ymlname:DeploywithAIValidationon:push:branches: [main]
jobs:validate:runs-on:ubuntu-lateststeps:-uses:actions/checkout@v4-name:Getdeploymentchangesid:changesrun:|
# Get commits since last deployment
last_deploy=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
if [ -n "$last_deploy" ]; then
changes=$(git log --oneline $last_deploy..HEAD)
else
changes=$(git log --oneline -10)
fi
echo "changes<<EOF" >> $GITHUB_OUTPUT
echo "$changes" >> $GITHUB_OUTPUT
echo "EOF" >> $GITHUB_OUTPUT
-name:AIRiskAssessmentid:assessuses:actions/github-script@v7with:script:|
// Analyze changes for deployment risk
const prompt = `
Analyze these changes for deployment risk:
${process.env.CHANGES}Return JSON:
{
"riskLevel":"low"|"medium"|"high",
"concerns": ["concern1", "concern2"],
"recommendations": ["rec1", "rec2"],
"requiresManualApproval":boolean
}
`;//CallAIandparseresponseconstanalysis=awaitcallAI(prompt);if(analysis.riskLevel==='high') {
core.setFailed('High-riskdeploymentdetected.Manualreviewrequired.');
}
returnanalysis;env:CHANGES:${{steps.changes.outputs.changes}}deploy:needs:validateruns-on:ubuntu-latestenvironment:productionsteps:-name:Deployrun:|
echo "Deploying to production..."
# Deployment commands here
3.3 Rollback Automation
# .github/workflows/rollback.ymlname:AutomatedRollbackon:workflow_dispatch:inputs:reason:description:"Reason for rollback"required:truejobs:rollback:runs-on:ubuntu-lateststeps:-uses:actions/checkout@v4with:fetch-depth:0-name:Findlaststableversionid:stablerun:|
# Find last successful deployment
stable=$(git tag -l 'v*' --sort=-version:refname | head -1)
echo "version=$stable" >> $GITHUB_OUTPUT
-name:Rollbackrun:|
git checkout ${{ steps.stable.outputs.version }}
# Deploy stable version
npm run deploy
-name:Notifyteamuses:slackapi/slack-github-action@v1with:payload:|
{
"text": "🔄 Production rolled back to ${{ steps.stable.outputs.version }}",
"blocks": [
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "*Rollback executed*\n• Version: `${{ steps.stable.outputs.version }}`\n• Reason: ${{ inputs.reason }}\n• Triggered by: ${{ github.actor }}"
}
}
]
}
