Loading...
Loading...
Found 1,536 Skills
fix PR review feedback: fetch unresolved threads, triage each finding skeptically, fix what holds, reply on threads, commit and push. Triggers: /fix-pr, address PR reviews. Reached by prath-mode after make-pr. Flags: --pr <n|url>, --no-push, --no-reply.
Automates the full code release pipeline — branch, commit, push, PR, wait for CI, merge, version bump, release, cleanup.
This skill should be used when the user needs to optimize a resume for software engineering, product management, or technical roles. Use when tailoring a tech resume to emphasize engineering contributions, open-source work, system design, or technical leadership for software and product positions.
Render the current plan as a high-DPI PNG dependency DAG — nodes are issues / sub-issues / PRs, edges come from sub-issue links plus dependency-language prose ("Depends on", "Part of", "Blocks", "Closes") and PR / commit cross-references, and every node is color-coded done / in-progress / available-next / blocked so sequencing and critical path are obvious at a glance. Use when asked "plan as dag", "draw a dag", "dag diagram", "show the dependency graph", "what's blocking what", "what's the critical path", "what can be parallelized", "what's left for
Use when a PR has reviews and is ready for final validation, to verify minimum 3 different agents reviewed and no critical concerns were raised before merging
Classifies every PR merged since the last tag into Keep a Changelog categories and writes the [Unreleased] section of CHANGELOG.md.
Review and process app submissions for the Pollinations showcase. Parse issues, validate submissions, create PRs, handle user corrections.
Resolve PR review comments
Detect and analyze potentially malicious repositories disguising as legitimate software cracks or pirated tools
make a pull request with a plain-English title and a thematic summary built from the branch diff. Triggers: open a PR, create a pull request, submit a PR. Flags: --target <branch> (default main), --ticket <id> (prefix title with the ticket), --conventional (conventional-commit title).
Create a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.
Cache Playwright browser binaries in CI/CD pipelines (GitHub Actions, Azure DevOps) to avoid 1-2 minute download overhead on every build.