ds-jury
From the author
Gets independent reviews of a change from two or three different models or providers and loops on fixes until they agree. Use when the user says jury, panel review, second opinions, ask other models, or /ds-jury.
Install
npx skills add aicodeking/deepseek-stack --skill ds-jury -a claude-code
Installs to .claude/skills/ds-jury/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 84
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- cross-model-reviewNoobyGains/godmodeUse when a reviewed change is about to land on a shared branch, be released or be deployed, and when the user asks for a second opinion on a change from a different model or a different AI vendor.Engineering★ 117
- ds-review-loopaicodeking/deepseek-stackRuns an author and a fresh-context reviewer in a loop on the current change until both agree it is correct, for at most four rounds. Use before or after filing a PR, when the user says review loop, get it reviewed, or /ds-review-loop.Engineering★ 166
- adjudicate-reviewpedrohcgs/claude-code-my-workflowTurn an incoming set of findings — from an AI reviewer, a referee report, a code review, a linter, or a second model — into verified fixes, without letting a confident misread damage correct work. Every finding is a CANDIDATE until checked against the actual source. Use whenever you receive review comments, audit findings, or a critique you did not write yourself, especially when the reviewer is a model or when the volume is too large to check by feel.Engineering★ 1.7K
- code-reviewcbrock84/headcountConducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.Engineering★ 2.6K
- review-responseNoobyGains/godmodeUse when code review feedback arrives from the user, a reviewer subagent, another model, a human colleague or an automated tool, before changing any code in response, and especially when the feedback is unclear, looks wrong, or contains several items that may depend on each other.Engineering★ 117
- reviewhashgraph-online/awesome-codex-pluginsGive advisory feedback on a plan, design or code change. Use when: asked for an opinion or a look-over, even informally. Not for acceptance; use Validate.Engineering★ 1.5K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in