一键导入
fix-issue
End-to-end implementation workflow for a GitHub issue from planning through PR creation. Use when starting work on an issue from scratch.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
End-to-end implementation workflow for a GitHub issue from planning through PR creation. Use when starting work on an issue from scratch.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Triage and fix application-code vulnerabilities reported as GitHub Security Advisories (GHSAs) in the Onyx repo. Use when the user mentions a GHSA ID, a CVE that affects Onyx source code, a security advisory URL, or asks to investigate or remediate a reported vulnerability. Out of scope (refer the user elsewhere) when the fix is purely a dependency version bump.
Iteratively improves a PR until Greptile gives it a 5/5 confidence score with zero unresolved comments. Triggers Greptile review, fixes all actionable comments, pushes, re-triggers review, and repeats. Use when the user wants to fully optimize a PR against Greptile's code review standards.
| name | fix-issue |
| description | End-to-end implementation workflow for a GitHub issue from planning through PR creation. Use when starting work on an issue from scratch. |
| category | github |
Complete workflow for implementing a GitHub issue from start to finish.
# 1. Fetch issue and create branch
gh issue view <issue>
git checkout -b <issue>-<description>
# 2. Commit and PR
git commit -am "feat: description"
git push
gh pr create --issue <issue>
gh issue view <issue> --comments - understand requirements, prior contextgit checkout -b <issue>-<description>Format: <issue-number>-<description>
Examples:
42-add-tensor-ops73-fix-memory-leak105-update-docsFollow conventional commits:
type(scope): Brief description
Detailed explanation of changes.
Closes #<issue-number>
Types: feat, fix, docs, refactor, test, chore
Before creating PR:
| Problem | Solution |
|---|---|
| Issue not found | Verify issue number |
| Branch exists | Use different name or delete old branch |
| Tests fail | Fix code before creating PR |
| CI fails | Address issues before merge |