Loading...
Loading...
Found 89 Skills
Use when scanning for and cleaning up code slop — duplicate patterns, dead code, misplaced files, and accidentally committed files.
PR triage: audit open PRs, deep review selected ones, draft and post review comments. Args: "all" to review all, PR numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
Ship workflow: merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR.
Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.
Auto-updates GitHub issues with commit progress. Use when starting work on an issue, tracking progress during implementation, or completing work with a PR.
Generate daily standup reports from git history, PRs, and a persistent work log. Use when the user says "daily", "standup", "what did I do yesterday", "generate my daily", "daily sync", or asks for a summary of recent work.
Branch and PR workflow for Engram contributors. Trigger: When starting any change that will be proposed through GitHub.
Bulk resolve unresolved PR review threads. Useful after manually addressing threads or after using /pr-threads-address.
Set up and conduct media monitoring to track brand mentions, sentiment, and share of voice across news, social, and online channels. Use this skill when the user needs to track what's being said about their brand, monitor competitors' media presence, detect emerging PR issues early, or measure campaign reach — even if they say 'what are people saying about us', 'monitor our brand mentions', 'track competitor PR', or 'set up media alerts'.
Fix only small, high-certainty OpenClaw bugs from a pasted issue/PR list after deep code review.
End-to-end orchestration for non-trivial software feature development. Use this skill whenever the user asks to implement a PR-sized feature, break down a plan, have subagents review a plan, run a plan-review-development-acceptance loop, coordinate multiple review perspectives, produce an acceptance report, or generate an HTML PR summary. Prefer this skill for multi-step code changes even if the user only says "build this feature" and the task is not a tiny one-file edit.
Submit a code review to GitHub via the GitHub API. Use this as the final step in a code review pipeline to post review findings to a PR.