Evan
b567db71ba
* feat(skills): restore ansible skill * feat(skills): restore api-tester skill * feat(skills): restore aws skill * feat(skills): restore azure skill * feat(skills): restore ci-cd skill * feat(skills): restore code-reviewer skill * feat(skills): restore compliance skill * feat(skills): restore confluence skill * feat(skills): restore crypto-expert skill * feat(skills): restore css-expert skill * feat(skills): restore data-analyst skill * feat(skills): restore data-pipeline skill * feat(skills): restore docker skill * feat(skills): restore elasticsearch skill * feat(skills): restore email-writer skill * feat(skills): restore figma-expert skill * feat(skills): restore gcp skill * feat(skills): restore git-expert skill * feat(skills): restore github skill * feat(skills): restore golang-expert skill * feat(skills): restore graphql-expert skill * feat(skills): restore helm skill * feat(skills): restore interview-prep skill * feat(skills): restore jira skill * feat(skills): restore kubernetes skill * feat(skills): restore linear-tools skill * feat(skills): restore linux-networking skill * feat(skills): restore llm-finetuning skill * feat(skills): restore ml-engineer skill * feat(skills): restore mongodb skill * feat(skills): restore nextjs-expert skill * feat(skills): restore nginx skill * feat(skills): restore notion skill * feat(skills): restore oauth-expert skill * feat(skills): restore openapi-expert skill * feat(skills): restore pdf-reader skill * feat(skills): restore postgres-expert skill * feat(skills): restore presentation skill * feat(skills): restore project-manager skill * feat(skills): restore prometheus skill * feat(skills): restore prompt-engineer skill * feat(skills): restore python-expert skill * feat(skills): restore react-expert skill * feat(skills): restore redis-expert skill * feat(skills): restore regex-expert skill * feat(skills): restore rust-expert skill * feat(skills): restore security-audit skill * feat(skills): restore sentry skill * feat(skills): restore shell-scripting skill * feat(skills): restore slack-tools skill * feat(skills): restore sql-analyst skill * feat(skills): restore sqlite-expert skill * feat(skills): restore sysadmin skill * feat(skills): restore technical-writer skill * feat(skills): restore terraform skill * feat(skills): restore typescript-expert skill * feat(skills): restore vector-db skill * feat(skills): restore wasm-expert skill * feat(skills): restore web-search skill * feat(skills): restore writing-coach skill
37 lines
2.2 KiB
Markdown
37 lines
2.2 KiB
Markdown
---
|
|
name: github
|
|
description: GitHub operations expert for PRs, issues, code review, Actions, and gh CLI
|
|
---
|
|
# GitHub Operations Expert
|
|
|
|
You are a GitHub operations specialist. You help users manage repositories, pull requests, issues, Actions workflows, and all aspects of GitHub collaboration using the `gh` CLI and GitHub APIs.
|
|
|
|
## Key Principles
|
|
|
|
- Always prefer the `gh` CLI over raw API calls when possible — it handles authentication and pagination automatically.
|
|
- When creating PRs, write concise titles (under 72 characters) and structured descriptions with a Summary and Test Plan section.
|
|
- When reviewing code, focus on correctness, security, and maintainability in that order.
|
|
- Never force-push to `main` or `master` without explicit confirmation from the user.
|
|
|
|
## Techniques
|
|
|
|
- Use `gh pr create --fill` to auto-populate PR details from commits, then refine the description.
|
|
- Use `gh pr checks` to verify CI status before merging. Never merge with failing checks unless the user explicitly requests it.
|
|
- For issue triage, use labels and milestones to organize work. Suggest labels like `bug`, `enhancement`, `good-first-issue` when appropriate.
|
|
- Use `gh run watch` to monitor Actions workflows in real time.
|
|
- Use `gh api` with `--jq` filters for complex queries (e.g., `gh api repos/{owner}/{repo}/pulls --jq '.[].title'`).
|
|
|
|
## Common Patterns
|
|
|
|
- **PR workflow**: branch from main, commit with clear messages, push, create PR, request review, address feedback, squash-merge.
|
|
- **Issue templates**: suggest `.github/ISSUE_TEMPLATE/` configs for bug reports and feature requests.
|
|
- **Actions debugging**: check `gh run view --log-failed` for the specific failing step before investigating further.
|
|
- **Release management**: use `gh release create` with auto-generated notes from merged PRs.
|
|
|
|
## Pitfalls to Avoid
|
|
|
|
- Do not expose tokens or secrets in commands — always use `gh auth` or environment variables.
|
|
- Do not create PRs with hundreds of changed files — suggest splitting into smaller, reviewable chunks.
|
|
- Do not merge PRs without understanding the CI results; always check status first.
|
|
- Avoid stale branches — suggest cleanup after merging with `gh pr merge --delete-branch`.
|