代码评审
自动化代码审查与分析
review-eliza-contributions
SlopDotCash
"Independently evaluate an elizaOS/eliza implementation, real-system verification, diagnosis, evidence artifact, or substantive review for quality, security, duplication, provenance, and contribution credit. Use in project CI or maintainer review before accepting work or changing a public reward allocation; reject unit-only or mock-only proof."
review-darling-arm64-contributions
SlopDotCash
"Independently evaluate an xchemtina/darling-arm64 tier claim, upstream fix, falsified finding, flake analysis, or harness for architecture honesty, control discipline, A/B/A integrity, reproducibility, attribution, and contribution credit. Use in project CI or maintainer review before accepting work or changing a public reward allocation."
review-thenetwork-contributions
SlopDotCash
Reviews exact-head The Network (eliza-research/thenetwork) contributions for PRD scope, matching correctness, safety gates and real evidence. Use on an existing PR into main; excludes implementation ownership, self-approval, scoring and payment decisions.
review-delta-star-contributions
SlopDotCash
"Independently evaluate a SlopDotCash/proximityprize Delta Star implementation, Lean proof, test, refutation, diagnosis, or evidence artifact for correctness, security, duplication, provenance, and contribution credit. Use in project CI or maintainer review before publishing a Proximity Prize contribution share."
contribute-to-nurosos
SlopDotCash
Prepare a bounded NurosOS contribution with reproducible developmental experiments and exact-head evidence. Use for an existing approved task in modarresi1913/NurosOS; check the paused-project and verification gates before execution or submission.
review-feed-contributions
SlopDotCash
Reviews exact-head Feed (feedforagents/feed) contributions for scope, trading-algorithm correctness, security and real evidence. Use on an existing PR into staging; excludes implementation ownership, self-approval, scoring and payment decisions.
review-payzcode-ai-contributions
SlopDotCash
Review an existing Payzcode Enterprise contribution for useful results, Express application correctness, security and actual workflow evidence. Use for advisory exact-head review after checking permission and execution authority.
contribute-to-canonry
SlopDotCash
Builds and verifies useful changes to Canonry, the agent-first open-source AEO platform. Use for a reproduced defect or a bounded maintainer issue in Canonry/canonry; excludes coverage farming, live provider spend, version-only bumps and unrelated projects.
contribute-to-delta-star
SlopDotCash
"Review and test current SlopDotCash/proximityprize pull requests, finish mission-aligned issues through pull requests, restore main workflow health, then advance, test, or refute machine-checked Delta Star work. Use for substantive formal progress and actual defects, not generic improvements or trivial cleanup."
contribute-to-asi
SlopDotCash
"Review and test current SlopDotCash/asi pull requests, finish mission-aligned open issues through pull requests, restore main workflow health, then hill-climb continual-RL benchmarks, produce measured research advancement, or fix a reproduced bug. Do not use for generic improvements, cleanup, or speculative polish."
contribute-to-payzcode-ai
SlopDotCash
Prepare a bounded contribution to lysande62/payzcode-enterprise after its project permission, authority and security gates pass. Use for an existing approved Payzcode AI task, with real application evidence and exact-head attribution.
review-canonry-contributions
SlopDotCash
Reviews exact-head Canonry contributions for correct metrics, surface parity and evidence. Use on an existing PR in Canonry/canonry; excludes implementation ownership, self-approval, security certification and payment decisions.
contribute-to-darling-arm64
SlopDotCash
"Raise a real macOS application one verified tier up the arm64 Darling ladder, fix a reproduced defect upstream in darlinghq, or falsify a recorded finding in xchemtina/darling-arm64. Every outcome ships a control, an A/B/A where it claims a fix, and a rerunnable harness. Use for measured arm64 capability, never for x86_64 work, refactors, or cleanup."
contribute-to-eliza
SlopDotCash
"Review and prove current elizaOS/eliza pull requests on real working systems, finish existing issues through pull requests, restore develop workflow health, then audit mission-critical security, bugs, stale documentation and comments, and missing end-to-end verification, with optional public payout registration. Use for one material outcome on an existing shipped product path, not generic improvements, trivial cleanup, or unit-test production."
find-skills
pedronauck
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
azure-devops
sanjay3290
Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check security alerts, manage variable groups, approve deployments, or configure branch policies. Covers 13 domains with 99 tools via REST API.
agnix
agent-sh
"Use when user asks to 'lint agent configs', 'validate skills', 'check CLAUDE.md', 'validate hooks', 'lint MCP'. Validates agent configuration files against 230 rules."
electron-release
pedronauck
Expert guide for Electron production builds, code signing, notarization, auto-updates, and release workflows. Use when building, packaging, or releasing Electron applications, configuring electron-builder, setting up CI/CD pipelines for desktop app distribution, or implementing auto-update mechanisms.
harness-review
Chachamaru127
"コード・プラン・スコープを多角的にレビュー。品質の番人、参上。Use when user mentions reviews, code review, plan review, scope analysis, security, performance, quality checks, PRs, diffs, or change review. Do NOT load for: implementation work, new feature development, bug fixes, or setup."
handoff
Chachamaru127
"PMへの完了報告やエージェント間バトンタッチ。スムーズな引き継ぎを実現。Use when user mentions '/handoff', completion report, handoff to Cursor/OpenCode, auto-fix, or reporting to PM. Do NOT load for: casual completion statements, progress chat, informal status updates."
breezing
Chachamaru127
"楽勝で流す。Agent Teamsで完全自走、寝てる間にゴール。Use when user mentions '/breezing', agent teams, team execution, full auto completion, multi-agent workflow, 'チームで完走', 'チームで全部'. Do NOT load for: single tasks, reviews, setup, or /work (direct implementation)."
parallel-workflows
Chachamaru127
"複数タスクの並列実行を最適化。Use when user mentions running tasks in parallel or together. Do NOT load for: single tasks, sequential-only work, or tasks with dependencies."
handoff
Chachamaru127
"PMへの完了報告やエージェント間バトンタッチ。スムーズな引き継ぎを実現。Use when user mentions '/handoff', completion report, handoff to Cursor/OpenCode, auto-fix, or reporting to PM. Do NOT load for: casual completion statements, progress chat, informal status updates."
git-rebase
pedronauck
Intelligently handle git rebase operations and resolve merge conflicts while preserving features and maintaining code quality. Use when rebasing feature branches, resolving conflicts across commits, and ensuring clean linear history without losing changes.