菜单
Use the GitHub CLI (gh) to manage issues, pull requests, labels, and repo metadata; includes safe body formatting with temp files or HEREDOCs to avoid shell mangling.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guide through tasks where project dependencies must be added.
Manage Vikunja tasks, projects, and labels through the Vikunja REST API. Load always whenever the user mentions Vikunja, tasks, todos, task management, project organization, or asks to create/list/update/delete tasks and projects in Vikunja.
Perform deep best-practices audits for any software project (frontend, backend, APIs, mobile, data/ML, infra). Use when users ask to audit architecture, code quality, scalability, maintainability, reliability, security posture, or "what should be improved" across a codebase.
Guide Opencode through coding tasks where git should be utilized. Use when the user asks to implement a specific change and commit it, or says "commit this," "make the change and commit," or similar. Also use for branch creation, listing, cleanup, and management tasks.
Guide through tasks where database migrations must be added. Use when users ask to add migrations, run migrations, rollback changes, or modify database schema.
Reviews GitHub pull requests with structured findings on code quality, security, performance, and test coverage. Use when user asks to "review PR", "review pull request", "review 123", "review owner/repo#123", "review https://github.com/owner/repo/pull/123", or similar PR review requests. Always attempts to clone the repo and create a worktree for full git analysis before resorting to API-only review. Never proceeds with degraded review without explicit user permission.
| name | github |
| description | Use the GitHub CLI (gh) to manage issues, pull requests, labels, and repo metadata; includes safe body formatting with temp files or HEREDOCs to avoid shell mangling. |
| license | MIT |
| author | DevTrev |
Use the GitHub CLI (gh) to manage issues, pull requests, checks, and related workflows. Prioritize safety, correctness, and clear formatting.
git remote -vgh repo view --json nameWithOwner,url--body-file.Example:
cat <<'EOF' > .tmp_issue.md
## Summary
<one-paragraph summary>
## Problem
<what is wrong>
## Proposal
- <bullet list>
## Acceptance Criteria
- <bullet list>
## Context
<links or file paths>
EOF
gh issue create --title "<title>" --label "backend,enhancement" --body-file .tmp_issue.md
rm .tmp_issue.md
cat <<'EOF' > .tmp_issue.md
<full updated body>
EOF
gh issue edit <number> --body-file .tmp_issue.md
rm .tmp_issue.md
Example:
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
- <bullet>
- <bullet>
## Testing
- <command>
EOF
)"
gh pr edit <number> --title "<title>"
gh pr edit <number> --body "$(cat <<'EOF'
<updated body>
EOF
)"
List labels before selecting:
gh label list --limit 200
gh repo view.--body-file or HEREDOC to avoid shell parsing.-i).