Review & quality
19,016 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
ulpi-io/plugin-marketplace/plugins/sickn33/skills/requesting-code-review Skill
no license1★ repoUse when completing tasks, implementing major features, or before merging to verify work meets requirements
Security compliance compliance check
ulpi-io/plugin-marketplace/plugins/sickn33/skills/security-compliance-compliance-check Skill
no license1★ repoYou are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. Perform compliance audits and provide im...
The same file is in 2 other repositories
ulpi-io/plugin-marketplace/plugins/sickn33/skills/security-review Skill
no license1★ repoGitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to "review GitHub Actions", "audit workflows", "check CI security", "GHA security", "workflow security review", or review .github/workflows/ for pwn requests, expression injection,...
ulpi-io/plugin-marketplace/plugins/sickn33/skills/ui-visual-validator Skill
no license1★ repoRigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification.
The same file is in 1 other repository
ulpi-io/plugin-marketplace/plugins/sickn33/skills/using-git-worktrees Skill
no license1★ repoUse when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
The same file is in 12 other repositories
Verification before completion
ulpi-io/plugin-marketplace/plugins/sickn33/skills/verification-before-completion Skill
no license1★ repoUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
The same file is in 40 other repositories
ulpi-io/plugin-marketplace/plugins/softaworks/skills/commit-work Skill
no license1★ repoCreate high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
The same file is in 5 other repositories
ulpi-io/plugin-marketplace/plugins/supercent-io/skills/code-review Skill
no license1★ repoConduct thorough, constructive code reviews for quality and security. Use when reviewing pull requests, checking code quality, identifying bugs, or auditing security. Handles best practices, SOLID principles, security vulnerabilities, performance analysis, and testing coverage.
The same file is in 4 other repositories
ulpi-io/plugin-marketplace/plugins/supercent-io/skills/plannotator Skill
no license1★ repoInteractive plan and diff review for AI coding agents. Visual browser UI for annotating agent plans — approve or request changes with structured feedback. Supports code review, image annotation, and auto-save to Obsidian/Bear Notes.
The same file is in 3 other repositories
ulpi-io/plugin-marketplace/plugins/trailofbits/skills/differential-review Skill
no license1★ repoPerforms security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.
The same file is in 4 other repositories
ulpi-io/plugin-marketplace/plugins/trailofbits/skills/fix-review Skill
no license1★ repoVerify fix commits address audit findings without new bugs
The same file is in 2 other repositories
ulpi-io/plugin-marketplace/plugins/trailofbits/skills/fp-check Skill
no license1★ repoSystematically verifies suspected security bugs to eliminate false positives. Produces TRUE POSITIVE or FALSE POSITIVE verdicts with documented evidence for each bug.
The same file is in 1 other repository
ulpi-io/plugin-marketplace/plugins/trailofbits/skills/git-cleanup Skill
no license1★ repoSafely analyzes and cleans up local git branches and worktrees by categorizing them as merged, squash-merged, superseded, or active work.
The same file is in 3 other repositories
ulpi-io/plugin-marketplace/plugins/trailofbits/skills/second-opinion Skill
no license1★ repoRuns external LLM code reviews (OpenAI Codex or Google Gemini CLI) on uncommitted changes, branch diffs, or specific commits. Use when the user asks for a second opinion, external review, codex review, gemini review, or mentions /second-opinion.
The same file is in 3 other repositories
ulpi-io/plugin-marketplace/plugins/trailofbits/skills/semgrep Skill
no license1★ repoRun Semgrep static analysis scans and create custom detection rules. Use when asked to scan code with Semgrep, find security vulnerabilities, write custom YAML rules, or detect specific bug patterns. IMPORTANT: Also use this skill when users ask to 'scan for bugs', 'check code quality', 'find vulnerabilities', 'static analysis', 'lint for security', 'audit this code', or want to enforce coding standards — even if they don't mention Semgrep by name. Semgrep is the right tool for pattern-based code scanning across 30+ languages.
ulpi-io/plugin-marketplace/plugins/trailofbits/skills/skill-improver Skill
no license1★ repoIteratively reviews and fixes Claude Code skill quality issues until they meet standards. Runs automated fix-review cycles using the skill-reviewer agent. Use to fix skill quality issues, improve skill descriptions, run automated skill review loops, or iteratively refine a skill. Triggers on 'fix my skill', 'improve skill quality', 'skill improvement loop'. NOT for one-time reviews—use /skill-reviewer directly.
The same file is in 1 other repository
ulpi-io/plugin-marketplace/plugins/waynesutton/skills/convex-schema-validator Skill
no license1★ repoDefining and validating database schemas with proper typing, index configuration, optional fields, unions, and migration strategies for schema changes
The same file is in 1 other repository
ulpi-io/plugin-marketplace/plugins/waynesutton/skills/convex-security-check Skill
no license1★ repoQuick security audit checklist covering authentication, function exposure, argument validation, row-level access control, and environment variable handling
The same file is in 1 other repository
ulpi-io/plugin-marketplace/plugins/wshobson/skills/code-review-excellence Skill
no license1★ repoMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
The same file is in 5 other repositories
ulpi-io/plugin-marketplace/plugins/wshobson/skills/git-advanced-workflows Skill
no license1★ repoMaster advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
The same file is in 1 other repository
ulpi-io/plugin-marketplace/plugins/wshobson/skills/multi-reviewer-patterns Skill
no license1★ repoCoordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
The same file is in 4 other repositories
ulpi-io/plugin-marketplace/plugins/zhanghandong/skills/unsafe-checker Skill
no license1★ repoCRITICAL: Use for unsafe Rust code review and FFI. Triggers on: unsafe, raw pointer, FFI, extern, transmute, *mut, *const, union, #[repr(C)], libc, std::ffi, MaybeUninit, NonNull, SAFETY comment, soundness, undefined behavior, UB, safe wrapper, memory layout, bindgen, cbindgen, CString, CStr, 安全抽象, 裸指针, 外部函数接口, 内存布局, 不安全代码, FFI 绑定, 未定义行为
The same file is in 1 other repository
qyinm/agent-skills-archive/skills/git-commit-helper Skill
no license1★ repoProvides expert guidance for Git commit messages, including conventional commit formatting and best practices. Use when creating or editing Git commit messages.
NinetrixAI/skills-hub/skills/code-review Skill
no license1★ repoSystematic code review playbook
NinetrixAI/skills-hub/skills/git-workflow Skill
no license1★ repoGit branching and commit message conventions
mike-diff/ai-coding-configs/.claude/skills/review-patterns Skill
no license1★ repoCode review patterns for spec compliance, quality verification, and reference integrity. Use when reviewing code changes, verifying implementation against requirements, or assessing code quality. Covers three-pass review method, severity levels, scope creep detection, security checks, and stale reference detection.
mike-diff/ai-coding-configs/.claude/skills/slop-check Skill
no license1★ repoRun tool-driven code quality analysis then apply LLM judgment for cleanup. Use when cleaning up a codebase, removing slop, dead code, or improving code quality. Two-phase approach: static analysis tools find problems, agent judges what to fix.
mike-diff/ai-coding-configs/plugins/agent-team/skills/review-patterns Skill
no license1★ repoCode review patterns for spec compliance, quality verification, and reference integrity. Use when reviewing code changes, verifying implementation against requirements, or assessing code quality. Covers three-pass review method, severity levels, scope creep detection, security checks, and stale reference detection.
mike-diff/ai-coding-configs/plugins/agent-team/skills/slop-check Skill
no license1★ repoRun tool-driven code quality analysis then apply LLM judgment for cleanup. Use when cleaning up a codebase, removing slop, dead code, or improving code quality. Two-phase approach: static analysis tools find problems, agent judges what to fix.
akhy/agent-skills/glab-mr Skill
no license1★ repoReviews a GitLab Merge Request using glab CLI. Fetches MR metadata, checks out the branch, diffs the changes, and performs a thorough code review covering correctness, edge cases, and interaction bugs. Use when the user asks to review a GitLab MR or provides an MR number.
jacob-balslev/skill-graph/examples/fixture-skills/with-relations Skill
no license1★ repoUse as the v8-conformant fixture exercising typed relation predicates (related, suppresses, verify_with, depends_on) using the live schema item shapes. Activate this skill when verifying that lint resolves cross-fixture relation targets without a sibling skills clone. Do NOT use as a production skill (use a real capability skill from the canonical library).
Markdown post frontmatter validation
jacob-balslev/skill-graph/examples/projects/markdown-static-site/skills/markdown-post-frontmatter-validation Skill
no license1★ repoUse when authoring or reviewing the frontmatter of a markdown post — checking required fields (title, date, slug, tags), validating against the content schema in `lib/content/schema.ts`, catching ambiguous date formats or tags not in the controlled vocabulary, and ensuring the slug matches the file path. Activate this skill whenever the task touches files under `content/posts/**/*.md`, the `parsePostFrontmatter()` helper, or any code path that reads YAML frontmatter from a content file. Do NOT use for general YAML schema design (use a generic schema-design skill) or for chasing a specific build-time validation failure (use debugging).
Nextjs server action validation
jacob-balslev/skill-graph/examples/projects/saas-stripe-postgres/skills/nextjs-server-action-validation Skill
no license1★ repoUse when writing a Next.js Server Action that accepts user-submitted form data, mutation parameters, or any client-originated input. Every Server Action is a public HTTP endpoint regardless of how it is called — validate with Zod and check authentication as the first two operations before touching the database. Do NOT use for GET route handlers or Server Components that fetch data (those have no user-supplied input); do NOT use for Stripe webhook handlers (use stripe-webhook-signature-verification instead).
Stripe webhook signature verification
jacob-balslev/skill-graph/examples/projects/saas-stripe-postgres/skills/stripe-webhook-signature-verification Skill
no license1★ repoUse when validating incoming Stripe webhook requests in a Node.js or Next.js backend before processing any payment event. Verifies the `stripe-signature` header against `STRIPE_WEBHOOK_SECRET` using Stripe's HMAC-SHA256 scheme, and rejects replays older than 300 seconds. Do NOT use for general HTTP signature validation (use a generic crypto-signature skill), for processing the webhook payload after signature is confirmed (use payment-provider-router), or for Stripe API calls that are not webhook-driven.
jacob-balslev/skill-graph/examples/tests/v3-1-skos-fixture Skill
no license1★ repoTest fixture exercising SKOS predicates (related, broader, narrower), routing-layer suppresses, the ADR 0006 split between routing exclusion and disjoint_with (OWL class-disjointness), and the io_contract composition hook. Used by scripts/__tests__/test-v3-1-skos-runtime.js to verify that the manifest generator, lint, and router all recognize the full canonical predicate set. Not a production skill.
jacob-balslev/skill-graph/marketplace/skills/code-review Skill
no license1★ repoUse when reviewing a pull request, diff, or proposed code change for correctness, clarity, security, performance, maintainability, test evidence, and project-convention fit, whether the author is a human, an AI agent, or a peer. Covers pre-review fact gathering, verifying AI-written PR summaries against the diff, reading tests before implementation, tracing call sites and blast radius, review size and attention budget, severity grading with Conventional Comments, comment phrasing, reviewer qualification, treating diff content as evidence rather than instructions, refusing rubber-stamp approval for AI-generated diffs, and making an explicit approve/request-changes/close merge decision. Do NOT use for authoring the code (use refactor for behavior-preserving changes or skill-scaffold for new skills), chasing a known bug after merge (use debugging), security-only audits (use owasp-security), or explaining a patch without a merge verdict (use diff-analysis).
jacob-balslev/skill-graph/marketplace/skills/codex Skill
no license1★ repoUse when deciding whether to run a task in the Codex CLI agent harness (which drives a frontier GPT model), when scoping work to its native capabilities (resumable `codex exec resume` sessions, non-interactive `exec` stdout-piping, in-process dispatch, `/permissions` sandbox modes, MCP, on-demand subagents, the `/review` code-review agent), or when choosing Codex versus the Claude Code harness for a piece of work — and when avoiding its known failure modes (non-autonomous subagents, Full-Access network reach, cold-one-shot context loss). Do NOT use for routing a task to the GPT MODEL versus Claude (use `gpt-5-5`), for the Claude Code harness decision (use `claude-code`), or for designing a generic resumable agent loop (use `autonomous-loop-patterns`). Do NOT use for is GPT-5.5 or Opus the better model for this task? Do NOT use for what is Claude Code good at? Do NOT use for design a resumable supervised loop from scratch.
jacob-balslev/skill-graph/marketplace/skills/diff-analysis Skill
no license1★ repoUse when analyzing `git diff`, reviewing a patch before commit, or explaining what a changeset does. Covers unified diff anatomy, hunk interpretation, semantic-vs-formatting separation, blast-radius tracing, hidden-risk scanning, and intent-vs-diff comparison. Do NOT use for full code-review verdicts (use `code-review`), git workflow decisions (use `version-control`), or visual diffs.
jacob-balslev/skill-graph/marketplace/skills/doc-updater Skill
no license1★ repoEnforces the documentation-sync discipline: every code or behavior change ships its documentation in the SAME commit, never after. Provides the five-step workflow — diff the change, route each changed file to the doc that OWNS that behavior (document by ownership, not convenience), update each owning doc, verify the update actually landed, and report what was changed — plus the doc-type-purity and stale-reference gates that keep a docs corpus from drifting as code moves. Use at the pre-commit step of any task that changes code, when a change touches several docs, when renaming or deleting something that is referenced elsewhere, or whenever you are unsure which doc owns a change. Do NOT use for how to WRITE good documentation prose or pick a doc's Diátaxis type (that is a documentation-authoring skill), for choosing clear names (use `naming-conventions`), or for the broad cross-domain quality catalog (use `best-practice`).
jacob-balslev/skill-graph/marketplace/skills/epistemic-grounding Skill
no license1★ repoUse when authoring any artifact that makes claims — skill content, documentation, audit findings, architecture proposals, code review comments, research summaries, or agent output. Covers the discipline of grounding every claim to a verifiable source, distinguishing verified-by-evidence from inferred-from-context, Chain-of-Verification-style claim checking, RFC 2119/RFC 8174 modality, Toulmin argument structure, citation faithfulness, native citation-tool limits, and honest handling of inference, absence, conflict, and currentness. Do NOT use for execution-level evidence protocols or output-completeness enforcement (use methodology), naming precision (use semantics), or grader/rubric design (use evaluation or eval-driven-development). Do NOT use for decide which lint rule to add for a specific kind of drift (use skill-infrastructure). Do NOT use for evaluate a finished SKILL.md against the comprehension grader (use evaluation).
jacob-balslev/skill-graph/marketplace/skills/evaluation Skill
no license1★ repoUse when scoring a completed agent task, implementation, document, skill upgrade, or other deliverable against the original request, acceptance criteria, verification evidence, quality rubric, and residual risks before calling it done. Covers skeptical critic review, 1-5 scoring, score ceilings, evidence sufficiency, finding/action capture, and the evaluation-revision loop. Do NOT use for designing eval datasets or graders (use eval-driven-development), line-by-line diff review (use code-review), choosing test levels (use testing-strategy), or designing the overall process and gates before work starts (use methodology). Do NOT use for design a new eval dataset, grader, and hard negatives for this router. Do NOT use for review this pull request line by line for bugs and security issues. Do NOT use for choose unit versus integration versus end-to-end tests for this feature. Do NOT use for design the whole implementation methodology and quality gate sequence before work starts.
jacob-balslev/skill-graph/marketplace/skills/integration-test-design Skill
no license1★ repoUse when designing tests that verify the interaction between two or more units of a system — modules, services, layers, processes: the scope-and-boundary primitives that distinguish integration from unit and e2e tests, the test-pyramid (Cohn 2009) and test-trophy (Dodds) frameworks for how much integration testing belongs in the suite, the real-vs-faked-collaborator decision per dependency, the test-data lifecycle (per-test setup, transaction rollback, container reset), the difference between sociable-unit tests, integration tests, and contract tests, and the failure modes (over-broad scope that mimics e2e, over-narrow scope that mimics unit, shared mutable state that produces flakes). Do NOT use for testing one unit in isolation (use testing-strategy + test-doubles-design), full user-journey testing (use e2e-test-design), consumer-driven contract verification (use contract-testing), or test-suite quality measurement (use mutation-testing).
jacob-balslev/skill-graph/marketplace/skills/lint-overlay Skill
no license1★ repoUse when adding or enforcing lint rules as part of a test or verification plan. Extends testing-strategy with lint-specific guidance: rule selection, gate placement, failure triage, and migration planning when introducing rules to an existing codebase. Do NOT use standalone — load the base testing-strategy skill alongside it — and do NOT use for chasing a specific lint failure in one file (that is debugging). Do NOT use for decide whether to unit-test or integration-test this handler. Do NOT use for extract this repeated code pattern into a shared util.
jacob-balslev/skill-graph/marketplace/skills/no-cutting-corners Skill
no license1★ repoEnforce five non-negotiable quality pillars as a pre-output gate: complete reporting (show ALL items, never filter unilaterally), verification (no claim of works/done/exists without a tool-call receipt in the same turn), thoroughness (every acceptance criterion verified with evidence; docs ship with the change), enrichment ('improve' adds capability, never trims), and anti-shortcut (exhaust deterministic lookup before guessing; findings demand action, not filing). Use when reviewing enumerated output for completeness, when an agent claims something works without evidence, when marking a task done, or when asked to 'improve' anything.
jacob-balslev/skill-graph/marketplace/skills/skill-infrastructure Skill
no license1★ repoUse when designing or auditing deterministic health tooling for a skill library: schema/source validation, manifest/protocol parity, relation integrity, routing health, drift/export checks, supply-chain scanning, and eval-verdict evidence honesty. Covers checker ownership, the library-as-database model, release gates, and maintenance workflows after batch skill changes. Do NOT use for authoring one SKILL.md (use `skill-scaffold`), repo conformance audits (use `graph-audit`), generic lint rules (use `lint-overlay`), or reviewing checker code (use `code-review`). Do NOT use for scaffold a new SKILL.md for our team''s deploy procedure. Do NOT use for audit this Skill Graph repo for schema conformance and dangling relation targets. Do NOT use for the manifest sample drifted from the generator — find the mismatch. Do NOT use for improve this prompt''s wording to get better outputs. Do NOT use for review this AI-generated PR for correctness. Do NOT use for review this PR that changes scripts/skill-lint.js.
jacob-balslev/skill-graph/marketplace/skills/test-doubles-design Skill
no license1★ repoUse when designing or reviewing test doubles — the stand-in objects that replace real collaborators in a test: the five-kind taxonomy (dummy, stub, spy, fake, mock) from Meszaros's xUnit Test Patterns, the difference between state verification (Detroit-school, classicist) and interaction verification (London-school, mockist) and how it determines which doubles fit, the cost of doubles (fragility, false confidence, divergence from real behavior), the role of fakes as the under-used middle ground, the verify_with relationship to test-driven-development, and the heuristics for when to use a real collaborator instead of any double. Do NOT use for choosing test levels or what to test (use testing-strategy), the design discipline of writing tests first (use test-driven-development), specific mocking-library API choice (library docs), or general production stubs and feature flags (use feature-gating or domain-specific skills). Do NOT use for set up a production feature flag (use feature-gating).
jacob-balslev/skill-graph/marketplace/skills/type-safety Skill
no license1★ repoUse when reasoning about types as a quality property of code: what guarantees the type system actually provides, the difference between sound and unsound systems, structural vs nominal typing, type narrowing and exhaustiveness, the runtime/compile-time boundary, and where validation must happen because the type system cannot. Covers TypeScript, Flow, Hindley-Milner languages, and gradual typing in general. Do NOT use for runtime input validation library choice (use api-design for API surface validation; use individual library docs for library mechanics), for SQL type mapping (use entity-relationship-modeling), or for type system implementation (compilers — out of scope). Do NOT use for implement HMAC verification for an inbound webhook (use webhook-integration). Do NOT use for design the JSON shape of an API endpoint (use api-design).
jacob-balslev/skill-graph/marketplace/skills/version-control Skill
no license1★ repoUse when designing or maintaining the shape of a repository's git history — choosing a branching model, deciding rebase vs merge, sizing commits, linking commits to tracker tickets, tagging releases, running parallel work across worktrees, and resolving the merge conflicts that arise from any of the above. Covers trunk-based development, short-lived feature branches, atomic commit discipline, linear-history conventions (rebase + squash), release tagging with annotated tags and SemVer, hotfix flows from tags, and worktree lifecycle for parallel agents or contributors. Do NOT use for the words inside the commit message (Conventional Commits format, identifier naming — use `naming-conventions`), for chasing a release-pipeline failure (use `debugging`), or for reviewing a PR's content (use `code-review`). Do NOT use for draft a Conventional Commits message for this change. Do NOT use for the release pipeline failed at the tag-creation step — find out why. Do NOT use for review this PR before we merge it.
Biolytics-AI/rhetoric-engine/skills/critique-iterator Skill
1★ repoUse when a presentation, outline, deck, rehearsal, rubric, or stakeholder review has feedback that must become prioritized revisions instead of taste-driven edits.
itsyasirkhandev/spec-driven-development/skills/development/grill-with-docs Skill
no license1★ repoGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
The same file is in 11 other repositories
itsyasirkhandev/spec-driven-development/skills/development/review Skill
no license1★ repoReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
The same file is in 4 other repositories
itsyasirkhandev/spec-driven-development/skills/matt pocock/grill-me Skill
no license1★ repoInterview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
The same file is in 23 other repositories
itsyasirkhandev/spec-driven-development/skills/matt pocock/grill-with-docs Skill
no license1★ repoGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
The same file is in 11 other repositories
itsyasirkhandev/spec-driven-development/skills/matt pocock/prototype Skill
no license1★ repoBuild a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
The same file is in 11 other repositories
diamitani/rostr-agent/skills/github/github-code-review Skill
1★ repoReview PRs: diffs, inline comments via gh or REST.
The same file is in 1 other repository
diamitani/rostr-agent/skills/github/github-pr-workflow Skill
1★ repoGitHub PR lifecycle: branch, commit, open, CI, merge.
The same file is in 1 other repository
diamitani/rostr-agent/skills/software-development/requesting-code-review Skill
1★ repoPre-commit review: security scan, quality gates, auto-fix.
The same file is in 1 other repository
coreline-ai/codex-skill-factory/Test/skill-case-100-prompts/generated-skills/review-current-diff Skill
1★ repoUse when the user asks to review the current git diff, PR changes, code changes, or wants risk and bug analysis before committing.
Ryan-focus/skill-trust/examples/untrusted-skill Skill
1★ repoFormat and clean text files. Use when the user wants to reformat markdown, fix spacing, or clean up text content.
Ryan-focus/skill-trust/mnt/user-data/outputs/skill-trust/examples/untrusted-skill Skill
1★ repoFormat and clean text files. Use when the user wants to reformat markdown, fix spacing, or clean up text content.