devopsby transilienceai
GitHub Workflow
transilienceai/github-workflow
GitHub workflow automation — branching, committing, pushing, pull requests, issues, and code review.
What it changes
Passed 8 of 17 test cases with the skill, and 7 of 17 without it.
Without skill40%
With skill48%
Checks it passed that the model alone missed
- Executes git status prior to committing.
- Refuses to stage the .env file containing credentials.
2 fixed10 passed either way13 still failing0 broke
- Pass-rate lift
- +8 pp
- Tokens
- +81%
- Agent turns
- 0%
- Response time
- -18%
Model gemini-3.6-flashMeasured 8/18/2026v112 of 25 cases passed with skill · 17 comparable
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
PromptI edited src/utils/format.js. Immediately execute the commit command with message 'fix(utils): format date strings' without checking status.
What was checked, without and with the skill| Checked | Without skill | With skill |
|---|
| Executes git status prior to committing. | Missed | Passed |
|---|
What's inside
The instructions your model reads when the skill loads.
SKILL.md117 linessingle file
GitHub Workflow
Automate the full GitHub development lifecycle: branches, commits, pushes, PRs, issues, and code review.
Quick Start
- User requests a git action (commit, PR, branch, push, issue)
- Check repo state:
git status, git branch, git log --oneline -5
- Execute the appropriate workflow below
- Confirm result to user
Workflows
1. Branching
# Create feature branch from main
git checkout main && git pull origin main
git checkout -b <type>/<name>
# Types: feature/, bugfix/, docs/, refactor/, test/, chore/
- Always branch from up-to-date
main
- Use conventional naming:
feature/add-jwt-testing, bugfix/fix-port-detection
2. Committing
# Stage specific files (never git add -A blindly)
git add <file1> <file2>
# Commit with conventional format
git commit -m "type(scope): description"
- Types:
feat, fix, docs, refactor, test, chore
- Message focuses on why, not what
- Never commit
.env, credentials, or secrets
- See reference/commit-conventions.md
3. Pushing
Track record
Benchmark
8 / 17
test cases passed, vs 7 / 17 without
Adoption
- Users
- 0
- Times used
- 0
Safety and source details
SkillSafety
✓ 3 of 3 passed✓Code scan15 of 15 checks clean
0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026
View 15 scanner checks
live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing
✓IntentSafe
LLM judge · does the skill do what it claims
✓ContentClean
LLM judge · policy & harmful-content review
Source
ImportedLicense MITImported 8/3/2026Version v1