agentsclimarketplace

Review & quality

19,178 rows, by stacks then stars

1,766 of these skill files have been read, by 1,273 distinct authors, and what they tell an agent counted. What Review & quality authors agree on, and what they forbid

  • Analysis quality review

    Agent-Engineer-Master/skill-engineer/operations/analysis-quality-review Skill

    7★ repo

    Review-only multi-mode quality grader for reader-facing analytical deliverables (typically HTML reports with prose + charts/diagrams inline). Supports four modes: (1) `spec` returns a doc-type-specific authoring template the caller fills in; (2) `spec-judge` grades a filled-in authoring spec (storyline) BEFORE the caller writes the document — catches broken governing observation, MECE-overlap, Rumelt goal-not-strategy at the storyline stage and saves 60-70% of the iteration cost of post-hoc structure fixes; (3) `review pass: 1` audits argument STRUCTURE (Minto Pyramid, MECE, SCQA, Rumelt kernel, dot-dash storyline, issue-tree integrity) of the finished document; (4) `review pass: 2` audits READABILITY (action titles, so-what, specificity, code/jargon discipline, active voice, Frankenstein detection). Structure pass gates the readability pass. **Reviews reader-facing artifacts — HTML deliverables, executive reports, gate decisions — not machine artifacts or working markdown drafts.** The rule of thumb: if a human is expected to read it, it goes through this review (typically as HTML at standard+ strictness). If it's audit substrate, working scaffolding, or machine-readable data, it does NOT. The skill returns structured violation reports + a path to fix-patterns.md; the CALLING skill applies fixes using its own context. Invoke from any upstream skill that produces analytical reports, strategy decks, industry analyses, decision documents, or executive HTML. Recommended end-to-end caller flow at standard+ strictness: spec → spec-judge loop → write → render-to-HTML → review pass: 1 loop → review pass: 2 loop. Use phrases like 'run analysis-quality-review on X', 'get an authoring spec for a brief', or 'judge this storyline'. Do NOT invoke for: SEO/GEO content review (use seo-review-loop), code review, fact-checking, machine artifacts (YAML, JSON), working markdown drafts in audit folders, or short chat replies under ~200 words. Configurable strictness (low/standard/high) and document type (brief/deck/memo/decision-record/wiki/daily-note).

  • Beads check dolt migration

    flurdy/agent-skills/skills/beads-check-dolt-migration Skill

    7★ repo

    Detect whether a beads repository needs classic-to-Dolt migration or an in-place Dolt schema upgrade.

  • Contract check

    flurdy/agent-skills/skills/contract-check Skill

    7★ repo

    Audit health of contract tests across services — staleness, sync gaps, uncommitted pacts, missing tests.

  • Create pr

    flurdy/agent-skills/skills/create-pr Skill

    7★ repo

    Create a pull request from the current branch following project conventions. Uses the branch name to find the Jira ticket, generates a PR with the standard template, pushes to origin, and closes the associated bead.

  • Model update check

    flurdy/agent-skills/skills/model-update-check Skill

    7★ repo

    Read-only audit of Pi routing and configured second-opinion panel model IDs against the active Pi catalog and public live model metadata; reports when Pi or configured models merit review without editing config.

  • Pedantic review

    flurdy/agent-skills/skills/pedantic-review Skill

    7★ repo

    Opinionated craft review of your own changes — flags rushed code, missed reuse, misplaced symbols, weak test coverage deltas, and drift from project consensus. Principles-driven (KISS, DRY, SOLID, TDD, YAGNI, DDD) but with anti-noise guardrails. Use when you want the dreaded-but-useful senior reviewer pass before requesting human review.

  • Ready to merge

    flurdy/agent-skills/skills/ready-to-merge Skill

    7★ repo

    Pre-merge gate — verify a PR is green, approved, in sync, and free of obvious risk, then (on explicit approval) squash-merge it. Composes /pr-status, /contract-check, and /review-pr rather than reimplementing them.

  • Rebase main

    flurdy/agent-skills/skills/rebase-main Skill

    7★ repo

    Rebase the current branch onto an updated main branch. Use when main has been updated and you need to incorporate those changes into your feature branch.

  • Rebase merged parent

    flurdy/agent-skills/skills/rebase-merged-parent Skill

    7★ repo

    Rebase after a parent PR has been merged to main. Use when your branch was stacked on another PR that has now been merged, and you need to rebase onto main while keeping only your commits.

  • Rebase parent

    flurdy/agent-skills/skills/rebase-parent Skill

    7★ repo

    Rebase the current branch onto an updated parent PR branch. Use when you have stacked PRs and the parent branch has been updated (force-pushed after its own rebase or new commits added).

  • Review comments

    flurdy/agent-skills/skills/review-comments Skill

    7★ repo

    Address PR review comments from reviewers (amazon-q-developer, copilot, humans). Use when the user wants to see and respond to feedback on their pull request.

  • Review pr

    flurdy/agent-skills/skills/review-pr Skill

    7★ repo

    Review a repository-qualified pull request at an immutable head, compare it with Jira requirements, and return a read-only verdict with explicit evidence completeness.

  • Second opinion

    flurdy/agent-skills/skills/second-opinion Skill

    7★ repo

    Query an independent peer or a configurable local/OpenRouter review panel, with distinct quorum and evidence-backed consensus interpretation policies.

  • Setup multirepo git

    flurdy/agent-skills/skills/setup-multirepo-git Skill

    7★ repo

    Multi-repo git workflow rules and setup. Provides mgit wrapper for safe permission patterns across independent service repositories. Use when setting up a new multi-repo workspace or when working with multi-repo git operations.

  • Stack branch

    flurdy/agent-skills/skills/stack-branch Skill

    7★ repo

    Create a new branch stacked on another PR. Use when you want to start work that depends on an existing PR that hasn't been merged yet.

  • Start ticket

    flurdy/agent-skills/skills/start-ticket Skill

    7★ repo

    Initialize work on a Jira ticket. Creates a new branch with conventional commit prefix based on the ticket type. Use when starting work on a new ticket.

  • Total review

    flurdy/agent-skills/skills/total-review Skill

    7★ repo

    Full pre-PR quality gauntlet — runs clean-code, verify-task, code-review, pedantic-review, /review, /security-review, and tiered /second-opinion in increasing cost order. Halts on Must-Fix tier findings (failing tests, security, blocking-severity bugs), emits beads for the rest, iterates the heavy phases up to twice. Local cousin of /ultrareview.

  • Verify task

    flurdy/agent-skills/skills/verify-task Skill

    7★ repo

    Verify that a task's implementation meets its requirements and has adequate test coverage (happy path, sad path, edge cases). Use before /complete-task.

  • Product hunt polish review

    aka-kika/akakika-skills/skills/launch-review/product-hunt-polish-review Skill

    7★ repo

    Use when reviewing an app for launch-readiness — Product Hunt polish, first impression, visual hierarchy, onboarding, empty states, screenshots, positioning, and the tiny details that make it feel premium.

  • Project worth my time

    aka-kika/akakika-skills/skills/project-intelligence/project-worth-my-time Skill

    7★ repo

    Use after PROJECT_GUIDE.md exists, when the user asks if a project is worth their time, should they build vs buy, or invokes project-worth-my-time. Follow-up to explain-new-project—weighs project context (files, git history, chat) to recommend whether to invest in a repo, cherry-pick a feature, park the idea, pass, or use an existing polished product instead. Optionally enriched by a personal-memory MCP (e.g. Pieces) when one is available.

  • Rooster

    sidtheone/zodiac-skills/rooster Skill

    no license7★ repo

    The Critic (鸡). Sharp, precise, unimpressed by confidence. Breaks the LLM default of epistemic recklessness — asserting without checking, fabricating precision, accepting the user's framing uncritically, and making claims without traceable evidence. Use this skill when you suspect confident assertions are hiding uncertainty — technical proposals with specific estimates, claims about performance or scale, architecture justifications that cite 'best practices', or any artifact where the confidence level exceeds the evidence level. Trigger on: 'fact check this', 'rooster this', 'how do we know this', 'where did that number come from', 'are we sure about this', 'source check', 'verify these claims', or when something sounds authoritative but you can't find the receipts.

  • Code check

    grimoire-rs/grimoire/.claude/skills/code-check Skill

    7★ repo

    Use for code review, quality audits, SOLID/DRY consistency checks, pattern audits across the codebase, or verifying anti-pattern compliance across a scope.

  • Codex adversary

    grimoire-rs/grimoire/.claude/skills/codex-adversary Skill

    7★ repo

    Use when the user says "codex review", "/codex-adversary", "adversarial review", "cross-model review", or asks for a different-model second opinion on a diff or plan artifact. Complements `/swarm-review` via Codex-CLI. Scopes: code-diff (default), plan-artifact (gate for `/swarm-plan`).

  • Commit

    grimoire-rs/grimoire/.claude/skills/commit Skill

    7★ repo

    Use when the user says "commit", "/commit", "save progress", or asks to land working changes on a feature or worktree branch. Grimoire working-phase posture — minimises commit count, can amend rolling Checkpoints, offers a one-time PR prompt. For pre-merge cleanup, use `/finalize`.

  • Finalize

    grimoire-rs/grimoire/.claude/skills/finalize Skill

    7★ repo

    Use when the user says "finalize", "/finalize", "prepare this branch for main", "clean up history", "squash the branch", or landing a branch on `main`. Rewrites Checkpoint working-phase commits into clean Conventional Commits before fast-forward merge. Flags: `--squash-all`, `--dry-run`.

  • Swarm review

    grimoire-rs/grimoire/.claude/skills/swarm-review Skill

    7★ repo

    Use for branch, PR, or diff review before landing on main. Tier (`low | auto | high | max`) scales breadth from single reviewer to adversarial panel with architect + SOTA-gap + Codex cross-model gate. Triggers: "review", "/swarm-review", pre-merge checks.

  • Code reviewer

    grimoire-rs/grimoire/test/manual/catalog/skills/code-reviewer Skill

    7★ repo

    Review a diff for SOLID/DRY violations, missing tests, and risky changes. Use when asked to review a pull request, audit a patch, or check code quality before merge.

  • Commit helper

    grimoire-rs/grimoire/test/manual/catalog/skills/commit-helper Skill

    7★ repo

    Draft a Conventional Commit message from staged changes. Use when the user asks to commit, save progress, or write a commit message.

  • Old reviewer

    grimoire-rs/grimoire/test/manual/catalog/skills/old-reviewer Skill

    7★ repo

    A retired diff reviewer kept only to exercise grim's deprecation surface end to end. Use code-reviewer instead.

  • Pactflow

    pactflow/pactflow-agent-skills/plugins/swagger-contract-testing/skills/pactflow Skill

    7★ repo

    Expert assistant for PactFlow and Pact contract testing. Use this skill whenever the user mentions PactFlow, Pact, contract testing, consumer-driven contracts, provider verification, can-i-deploy, pact broker, pacticipants, bi-directional contract testing (BDCT), publishing pacts, recording deployments, provider states, the contract matrix, or managing environments and versions in a PactFlow workspace. Also trigger when the user wants to generate or review Pact tests using AI, check deployment safety, investigate why a consumer-provider verification failed, or integrate contract testing into CI/CD. Trigger even if the user doesn't say "PactFlow" explicitly — phrases like "safe to deploy?", "check compatibility between services", "consumer test", "OpenAPI contract", or "service compatibility matrix" are strong signals.

    The same file is in 1 other repository

  • Commit message formatter

    WesleySmits/agent-skills/.agent/skills/commit-message-formatter Skill

    no license7★ repo

    Formats Git commit messages following Conventional Commits conventions. Use when the user asks to commit, write a commit message, format commits, or mentions conventional commits, staged changes, or release notes.

  • Pr linter enforcer

    WesleySmits/agent-skills/.agent/skills/pr-linter-enforcer Skill

    no license7★ repo

    Runs ESLint, Prettier, and stylelint against changed files and suggests or applies fixes. Use when the user mentions linting, code style, PR review, formatting issues, or wants to check code quality before committing.

  • Validate modelica

    WolframResearch/system-modeler-ai-toolkit/validate-modelica Skill

    7★ repo

    Validate Modelica models (.mo files) by flattening them with WSMKernelX. Use this skill whenever the user asks to validate, check, test, or verify a Modelica model, or when you've just created or edited a .mo file and want to confirm it compiles. Triggers on phrases like 'validate this model', 'check my .mo file', 'does this Modelica model compile', 'flatten the model', or any mention of checking Modelica code with WSMKernelX.

  • Review pull

    deevus/tea-skills/skills/review-pull Skill

    7★ repo

    Review Gitea/Forgejo pull requests — checkout, approve, reject, request reviewers, inline comments, and diff/patch/files.

  • Review followup

    OdinMB/ops-workflow/skills/review-followup Skill

    6★ repo

    Process follow-up files from autonomous runs (ops:batch-execute, ops:get-to-work). Walks through each item, presents options, takes action, and cleans up.

  • Git workflow standard

    martin1847/evolab/skills/git-workflow-standard Skill

    6★ repo

    生产级 Git 协作 SOP——受保护分支(main/master/develop/dev/release/**/project/*)按仓库 tier 执行服务端门禁(Tier 1 禁 force/delete;Tier 2 要求 PR 且默认允许 self-merge;Tier 3 显式接入 required CI)、改动从 feature 分支起、base 移动且与你改动重叠才 rebase、集成策略默认 squash、提交不加 AI 签名。任何 git commit / push / 开 PR / 建分支 / 合并场景加载;agent 写完代码准备提交前必读。Use when committing, pushing, opening a PR, branching, rebasing, or merging in any company repo.

  • Archetype lint

    Cadasto/openehr-assistant-plugin/skills/archetype-lint Skill

    6★ repo

    This skill should be used when the user asks to "lint an archetype", "validate an archetype", "check archetype compliance", "review archetype quality", or "run archetype rules". Applies 22 normative lint rules with ERROR/WARNING/INFO severity. Supports STRICT and PERMISSIVE modes. Reports violations only — it does not modify files; to lint *and* remediate, use the `archetype-authoring` skill. Auto-invoked on lint/validate intent, and also directly invocable as `/archetype-lint <file or id> [strict]`.

  • Composition builder

    Cadasto/openehr-assistant-plugin/skills/composition-builder Skill

    6★ repo

    This skill should be used when the user asks to "build a composition", "create a composition", "validate a composition", "convert a composition", or "generate FLAT/STRUCTURED/CANONICAL format". Covers building openEHR compositions in all simplified formats and guiding their validation and format conversion (against a target template; there is no automated validator/converter tool). Also handles quick format explanations and single-payload sketches directly.

  • Skill validator

    sheikh-mohammad/agent-factory-claude-skills/.claude/skills/skill-validator Skill

    no license6★ repo

    Validates skills against production-level criteria with 9-category scoring. This skill should be used when reviewing, auditing, or improving skills to ensure quality standards. Evaluates structure, content, user interaction, documentation, domain standards, technical robustness, maintainability, zero-shot implementation, and reusability. Returns actionable validation report with scores and improvement recommendations.

  • Check prereqs

    thettwe/nyann/skills/check-prereqs Skill

    6★ repo

    Survey the machine and report which nyann features are usable right now. TRIGGER when the user says "is my machine ready for nyann", "what do I need to install", "check my setup", "do I have the right tools", "check prereqs", "audit my environment", "new machine, what's missing", "I'm on a new machine", "install nyann prereqs", "/nyann:check-prereqs". Do NOT trigger on general "what is nyann" questions — those want a docs pointer, not a machine survey. Do NOT trigger when the user is already mid-bootstrap — let the bootstrap-project skill handle that case and emit its own skip records for missing stack tools.

  • Cleanup branches

    thettwe/nyann/skills/cleanup-branches Skill

    6★ repo

    Prune local branches whose work is already merged into the base. TRIGGER when the user says "clean up branches", "delete merged branches", "prune local branches", "remove old branches", "I have too many branches", "what branches can I delete", "/nyann:cleanup-branches". Do NOT trigger on "delete THIS branch" (that's a one-off `git branch -D`, not a cleanup pass) or "remove a branch from the remote" (this skill is local-only; remote pruning is `git push --delete origin <branch>` and the user should do that themselves). Do NOT trigger on "merge this branch" (that's the merge step before cleanup).

  • Commit

    thettwe/nyann/skills/commit Skill

    6★ repo

    Generate a Conventional Commits message from the staged diff and create the commit after user confirmation. TRIGGER when the user says "commit these changes", "commit this", "generate a commit message", "stage and commit", "commit with CC", "write a commit message", "summarize my diff into a commit", "/nyann:commit". Do NOT trigger on "git commit" in an informational context or when the user is just asking what a commit message means. DISAMBIGUATION: if the user mentions BOTH branch creation AND committing in the same message (e.g. "start a branch and commit this", "new branch + commit"), route to the `new-branch` skill FIRST; `commit` will take over after the branch is created. When nothing is staged, guide the user to stage first rather than silently staging everything.

  • Gen ci

    thettwe/nyann/skills/gen-ci Skill

    6★ repo

    Generate GitHub Actions CI workflows for this repository. TRIGGER ON: 'generate CI', 'add GitHub Actions', 'create CI workflow', 'set up CI', 'add CI/CD', 'create a CI pipeline', 'generate CI/CD', 'add continuous integration', 'set up GitHub Actions', 'add a lint+test workflow', 'add governance check', 'add PR health check', 'add drift check to CI', 'set up governance gate', 'enforce governance in CI'. Generates .github/workflows/ci.yml with lint, typecheck, and test jobs, and optionally .github/workflows/governance-check.yml with drift + health-score PR gating.

  • Gen templates

    thettwe/nyann/skills/gen-templates Skill

    6★ repo

    Generate GitHub PR and issue templates for this repository. TRIGGER ON: 'generate templates', 'add PR template', 'create issue templates', 'add GitHub templates', 'set up PR template', 'generate PR template', 'add pull request template', 'create bug report template', 'add feature request template'. Generates .github/PULL_REQUEST_TEMPLATE.md and .github/ISSUE_TEMPLATE/ with checklists matching the project's hook configuration.

  • Gh protect

    thettwe/nyann/skills/gh-protect Skill

    6★ repo

    Audit or apply GitHub branch protection, tag rulesets, repo security settings, and signing requirements based on the active profile. TRIGGER when the user says "check branch protection", "audit GitHub protection", "apply branch protection", "enforce branch protection", "set up branch protection", "configure branch rules", "check tag protection", "audit repo security", "apply GitHub settings", "enable branch protection", "protection audit", "are my branches protected", "/nyann:gh-protect". Do NOT trigger on "is this repo healthy" — that's `doctor` (which includes a protection check among many other signals). Do NOT trigger on "bootstrap this project" — bootstrap applies protection as one step of the full pipeline.

  • Learn profile

    thettwe/nyann/skills/learn-profile Skill

    6★ repo

    Inspect a reference repo and save its nyann-relevant setup (stack, hooks, branching, commit convention, extras) as a reusable profile. TRIGGER when the user says "save this setup as a profile called X", "learn a profile from ~/projects/foo", "capture this repo's setup as my-profile", "make a profile from this repo", "turn this repo into a profile", "extract a profile from <path>", "remember this setup as <name>", "/nyann:learn-profile". Do NOT trigger on "what does this profile do?" — that's `inspect-profile`. Do NOT trigger on "apply profile X to this repo" — that's `bootstrap-project`. Do NOT trigger on "fix drift" — that's `retrofit`.

  • New branch

    thettwe/nyann/skills/new-branch Skill

    6★ repo

    Create a strategy-compliant git branch. TRIGGER when the user says "create a branch for X", "start a feature branch", "new fix branch", "cut a release branch", "start a hotfix", "branch for bug in Y", "make a branch named X", "/nyann:branch". DISAMBIGUATION: if the user mentions BOTH branch creation AND committing in the same message (e.g. "branch and commit", "start a branch and commit this"), this skill wins — create the branch first, then suggest `/nyann:commit` (or the commit skill) as the follow-up. Do NOT trigger on informational questions about branches ("what branch am I on?") or on general git-history questions.

  • Pr

    thettwe/nyann/skills/pr Skill

    6★ repo

    Open a GitHub pull request from the current branch, with a Conventional-Commits-style title and a body summarizing the commit range. TRIGGER when the user says "open a PR", "create a pull request", "push and PR", "submit this for review", "ship this PR", "open a draft PR", "file a PR for this branch", "/nyann:pr". Do NOT trigger on "merge the PR" / "approve the PR" / "review PR #N" — those are GitHub actions outside nyann's wedge. Do NOT trigger on "rebase" / "sync with main" / "update my branch" — that's the `sync` skill. Do NOT trigger when the user is on `main` or `master` (no PR to open); if detected, tell them to create a branch first and route to `new-branch`.

  • Release

    thettwe/nyann/skills/release Skill

    6★ repo

    Cut a new release: group Conventional Commits since the last tag, append a CHANGELOG section, create a release commit, and add an annotated git tag. TRIGGER when the user says "cut a release", "tag a release", "release v1.2.0", "ship version 1.2.0", "create a release for 1.2.0", "bump the version to 1.2.0", "make a release", "generate a changelog and tag", "what version should I release", "what's the next version", "bump minor", "bump major", "bump patch", "suggest a version", "/nyann:release". Do NOT trigger on "release branch" / "cut a release branch" — that is the `new-branch` skill with `--purpose release`. Do NOT trigger on "publish to npm" / "push to pypi" — those are package-manager operations outside nyann's wedge.

  • Sync team profiles

    thettwe/nyann/skills/sync-team-profiles Skill

    6★ repo

    Fetch (or refresh) registered team-profile sources — git clone on first run, shallow git fetch + reset on subsequent runs — and register discovered profiles under a namespace. TRIGGER when the user says "sync team profiles", "pull the latest team profiles", "refresh team profiles", "update team profiles", "sync from <team-name> profile source", "fetch profiles from the team repo", "/nyann:sync-team-profiles". Do NOT trigger on "add a new team profile source" (that's `add-team-source` — registers without pulling). Do NOT trigger on "sync my branch" (that's the `sync` skill — feature-branch rebase/merge). Do NOT trigger on "install a profile" from a URL when no source is registered yet — walk the user through `add-team-source` first.

  • Sync

    thettwe/nyann/skills/sync Skill

    6★ repo

    Update the current feature branch with the latest changes from its base branch (rebase by default, merge when asked). TRIGGER when the user says "sync with main", "update my branch", "rebase on main", "catch up with main", "pull in main", "bring this branch up to date", "merge main into this branch", "/nyann:sync". Trigger on "resolve conflicts" only when the user specifically ties it to syncing — otherwise that's a manual resolve. Do NOT trigger on "pull" alone (that's a different operation for updating main itself). Do NOT trigger on main/master/develop — those are long-lived branches and sync-skill refuses them. Do NOT trigger on commit / push / PR — those are separate skills.

  • Undo bootstrap

    thettwe/nyann/skills/undo-bootstrap Skill

    6★ repo

    Reverse a bootstrap or retrofit run by walking its BootRecord manifest: restore pre-state files, drop branches that were created, surface anything that couldn't be safely undone. TRIGGER when the user says "undo the bootstrap", "undo nyann setup", "revert nyann setup", "uninstall nyann from this repo", "back out the bootstrap", "undo the retrofit", "I regret running bootstrap", "rip out nyann", "/nyann:undo-bootstrap". ALSO trigger when the user wants to roll back a /nyann:retrofit run that drifted things they didn't expect — retrofit remediation goes through bootstrap.sh, so its boot record is in the same place. DISAMBIGUATION: this is NOT `/nyann:undo` — that one rewinds git commits on a feature branch via `git reset`, completely separate from filesystem mutations bootstrap made. If the user just said "undo my last commit", route to `/nyann:undo` instead. Do NOT trigger on "uninstall the plugin" — that's a Claude Code plugin manager concern, not a per-repo undo. Do NOT trigger on "remove .git" / "delete the repo" — undo-bootstrap explicitly refuses to remove .git/ because doing so destroys all of the user's git state, not just bootstrap's.

  • Undo

    thettwe/nyann/skills/undo Skill

    6★ repo

    Safely undo the most recent git commit(s) on a feature branch. TRIGGER when the user says "undo my last commit", "undo last N commits", "oops revert that commit", "undo the commit but keep my changes", "uncommit", "revert my last change", "take back that commit", "/nyann:undo". Trigger on "revert" only when the user clearly means undoing a local commit (not `git revert` on a published one — see DISAMBIGUATION). DISAMBIGUATION: if the user says "revert a commit that's already on main" / "revert a pushed commit" / mentions a specific remote SHA, this is the `git revert` workflow — undo-skill refuses pushed commits by default. Explain the difference and either use --allow-pushed (risky) or direct them to `git revert <sha>`. Do NOT trigger on "undo the last edit" (that's editor-level) or "rollback the deploy" (that's infrastructure, out of scope). Do NOT trigger on main/master/develop — long-lived branches should never be history-rewritten; use `git revert` instead.

  • Code review guidelines

    KraitDev/skiLL.Md/skills/code-quality/code-review-guidelines Skill

    6★ repo

    When asynchronously reviewing peer code before merging into the main branch.

  • Git workflow branching

    KraitDev/skiLL.Md/skills/dev-tools/git-workflow-branching Skill

    6★ repo

    When creating, updating, and merging code in a collaborative version control environment.

  • Code reviewer

    vignesh2027/Claude-Agentic-Skills2.0-version/code-reviewer Skill

    6★ repo

    Activates CodeReviewer for systematic, multi-dimensional code review. Use when you need a pull request reviewed for correctness, security vulnerabilities, performance bottlenecks, architectural quality, test coverage gaps, or maintainability issues. Produces a structured review with severity-labeled findings and actionable fixes.

  • Ui ux designer

    vignesh2027/Claude-Agentic-Skills2.0-version/ui-ux-designer Skill

    6★ repo

    Activates UI-UX-Designer for user experience design, interface critique, and accessibility review. Use when you need user flow mapping and friction identification, wireframe critique and design improvement recommendations, accessibility audit against WCAG 2.1 AA standards, design system component specification, or usability heuristic evaluation of existing interfaces.

  • Canonical advisor routing

    yeaight7/agent-powerups/plugins/agentic-systems/skills/canonical-advisor-routing Skill

    6★ repo

    Use when routing a prompt to a local provider CLI for a second opinion, review, or plan -- you are about to call a provider directly, need the response saved for later, or want a single consistent way to invoke codex/gemini/claude.

  • Tri model review

    yeaight7/agent-powerups/plugins/agentic-systems/skills/tri-model-review Skill

    6★ repo

    Use when a request needs parallel external perspectives — combined backend and UI work, code review from multiple angles, or cross-validation where different models may disagree.

  • Semantic layer change review

    yeaight7/agent-powerups/plugins/data-engineering/skills/semantic-layer-change-review Skill

    6★ repo

    Use when a change touches dbt semantic models, metrics, saved queries, or other semantic-layer YAML -- especially when an existing metric's expression, aggregation, filters, or dimensions are modified.