Loading...
Loading...
Found 587 Skills
Use whenever leaving comments on GitHub.
Use when the user asks to review one or more GitHub pull requests — "review PR #12", "review the open PRs", "check the PRs the agents opened" — in Claude Code, Codex, or any other agent. Not for reviewing uncommitted local changes.
Use when a factory run must post its changes — check out the run branch, commit a step's allowlisted paths, push only that branch, and open or reuse one draft MR/PR with milestone/assignee ownership. Also the shared home for factory run contracts (executor, tracker integration, lanes, brief and provider templates).
Find patterns worth sharing from recent PRs and repo history, both repeats to fix and good practices worth spreading. Use when a champion wants to know what the team should reuse or learn from.
Creates PR review reports. In addition to investigating bugs and vulnerabilities, it verifies the consistency between exported conversation contexts, PR descriptions, and implemented code, and critically scrutinizes the soundness of the implementer's work. Used when users say things like "Write a PR review report", "Conduct a code review with conversation context", or "Question the sanity of this PR".
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments. Identical to greploop, but triggers reviews by tagging @greptile-apps, which bypasses Greptile's file-count limit on huge PRs that the plain @greptile mention refuses to review. Use when the user wants to fully optimize a large PR/MR/CL against Greptile's code review standards.
Review an existing code change set for defects, regressions, risks, and maintainability issues. Use for open-ended review requests about a diff, branch, commit, pull request, or uncommitted changes. Do not use for running tests or other checks, verifying named requirements or claims, or diagnosing a specific known failure.
Implement or review code through a verified result. Keep changes small and TypeScript readable.
Review a pinned Git diff on two independent axes — repository standards and spec/behavior fidelity. Use when asked to review a branch, commit range, or PR against a fixed point; report evidence-backed findings without changing code, including correctness risks when no spec exists.
Gate a PR's merge without human review, and merge it when the gate passes. Use when landing a PR during autonomous work, or when another skill needs a merge gate.
日本語で文章を書く、直す、レビューするとき、日本語のコミットメッセージ、PR 説明、ドキュメント、UI 文言を書くときに参照する。このスキルは japanese スキルに統合した。内容は japanese スキルを使う。
Assess findings and feature opportunities, preserve related evidence and decisions, and recommend scoped next actions. Use for Just, Yak or Explore handoffs and decisions about a fix, improvement or PR.