All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 14,947
- 623
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse code review & quality skills
Showing 193–216 of 14,947 skills
- Vet AuditsAdversarially validate each finding in docs/AUDIT.md against the current code — is it real, worth solving, and actionable — then file the survivors as type:audit GitHub issues and drop the rest. Use when asked to vet, review, or prune the audit backlog before fixing it. Review only; it does not implement fixes.Votes: 0GitHub stars: 7
- Ship IssueTake one GitHub issue number or a free-form task all the way to a review-complete pull request — implement it, open the PR, get an independent rival-agent review, address the feedback, and repeat that review round at most twice, driving CI to green and the PR to mergeable. Stops there with the PR open by default; `mode=autonomous` also merges it. Use when asked to ship an issue, take an issue end to end, implement and get a PR reviewed, or drive one task from description to a PR that has surv...Votes: 0GitHub stars: 7
- Reconcile AdrsReview recent decisions from the current conversation and git history, verify existing ADRs still reflect reality, and add or amend ADRs as needed. Use at the end of a session that touched architecture, testing, infrastructure, or build tooling, or when asked to refresh or reconcile the ADRs.Votes: 0GitHub stars: 8
- Create Pr Review PromptBuild a copy-paste prompt directing another agent to review every PR this session produced with the leave-pr-review skill — enumerating each PR (a stacked campaign has several), then adding the spots that deserve special attention and an adversarial pass on the overall strategy as extra focus areas layered on top of a full review sweep. Use when asked to create a PR review prompt, a PR review or feedback handoff, to hand this session's PRs to an independent reviewer, or to prep a second-opini...Votes: 0GitHub stars: 7
- Burn Down Code SmellsRun an unattended code-quality campaign — audit the codebase principle by principle and then area by area with parallel read-only auditors, cluster the verified findings into small units, and ship each unit as its own rival-reviewed, CI-green, merged PR through ship-issue, several disjoint units at a time, until every finding is merged, rejected with a reason, or parked for the user; then fold what the run learned into docs/CODING-STANDARDS.md. Use when asked to burn down code smells, improve...Votes: 0GitHub stars: 7
- Audit CodeComprehensive repository pass that produces a prioritized list of performance, readability, maintainability, and architecture improvements in docs/AUDIT.md. Use when asked to audit the codebase, hunt for improvement opportunities, or do a broad code-quality sweep across the repo.Votes: 0GitHub stars: 7
- English ReplyUse when drafting English replies for GitHub issues, PR reviews, maintainers, release notes, or external collaboration.Votes: 0GitHub stars: 20
- Gh IssuesFetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]Votes: 0GitHub stars: 2
- Adaptive MemoryHierarchical memory management for AI agents across sessions. Maintains three layers — daily notes (raw logs), active context (working memory), and long-term memory (curated knowledge) — with automatic distillation from raw notes to permanent memory. Use when setting up persistent memory for an agent workspace, when an agent needs to remember context across sessions or compaction boundaries, when organizing what to remember vs. forget, or when consolidating scattered notes into structured lon...Votes: 0GitHub stars: 2
- Openclaw Pr MaintainerMaintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when Codex needs to validate bug-fix claims, search for related issues or PRs, apply or recommend close/reason labels, prepare GitHub comments safely, check review-thread follow-up, or perform maintainer-style PR decision making before merge or closure.Votes: 0GitHub stars: 2
- Claude Memory OptimizerStructured memory system with 4-type classification, frontmatter metadata, automated migration, and PUA-style maintenance checklist. Based on Claude Code memory architecture.Votes: 0GitHub stars: 2
- Query StateUse this skill when building or debugging URL-backed state with nuxt-ui-tools as a package consumer. Covers codecs, useQueryState, useQueryStates, dynamicQueryState, grouped state, dynamic keys, and practical query-string examples.Votes: 0GitHub stars: 2
- Nuxt Ui Tools RepoUse this skill when implementing or refactoring code inside the nuxt-ui-tools repository itself. It routes the agent to the canonical AGENTS.md guide and the deeper maintainer skill so the agent can understand where code belongs, how domains relate, how to extend features, and what maintenance surfaces must be kept in sync.Votes: 0GitHub stars: 2
- Nuxt Ui Tools ReactivityUse this skill for internal Vue reactivity and state-model work in the nuxt-ui-tools repository. Covers lean reactivity, query-state integration, when to use computed vs watch vs shallowRef, VueUse usage, and how to simplify over-layered state models.Votes: 0GitHub stars: 2
- Nuxt Ui Tools MaintainerUse this skill for internal maintenance and feature work in the nuxt-ui-tools repository. It explains the repository operating model, exact placement rules, how runtime domains relate, how features should be structured and extended, how consumer skills must be maintained, and what to keep in sync when changing the library.Votes: 0GitHub stars: 2
- Nuxt Ui Tools I18nUse this skill for internal i18n work in this repository. Covers locale ownership, provider wiring, lazy schema text contracts, and the maintenance surfaces that must stay in sync when package or playground translations change.Votes: 0GitHub stars: 2
- Civiltekk Ponytail Audit SkillOver-engineering audits and debt tracking — whole-repo audit (ranked delete/stdlib/native/yagni/shrink findings, net removable count, one-shot report), diff-only review (concrete replacements), and `ponytail:` comment harvest into a debt ledger (ceiling + upgrade trigger per marker, no-trigger rot). Triggers: audit for over-engineering, find bloat, what can I delete, over-engineered diff, simplify this change, review for bloat, ponytail shortcuts, what did ponytail defer, tech debt markers.Votes: 0GitHub stars: 6
- Guru Create TaskCreate an independently reviewed Trellis task in the exact acquired checkout, or recover its result without repeating mutation.Votes: 0GitHub stars: 8
- Qldp Entanglement BreakingUse when quantum privacy clashes with entanglement needs.Votes: 0GitHub stars: 3
- Proper Agnostic Learning Mps TtnUse when learning MPS or TTN states from arbitrary noisy states.Votes: 0GitHub stars: 3
- Boolean Threshold Neuron CapacityNeuron capacity from Boolean threshold function asymptotics.Votes: 0GitHub stars: 3
- Springboot TestingSpring Boot testing discipline — TDD workflow with JUnit 5, @SpringBootTest slicing (@WebMvcTest, @DataJpaTest), MockMvc, Testcontainers, and the verification gates a Spring Boot change must pass before it ships (build, coverage floor, static analysis, integration checks). Use when writing Spring Boot tests or verifying a Spring Boot change is done.Votes: 0GitHub stars: 12
- Context CompressionThis skill should be used when the user asks to "compress context", "summarize conversation history", "implement compaction", "reduce token usage", or mentions context compression, structured summarization, tokens-per-task optimization, or long-running agent sessions...Votes: 0GitHub stars: 8
- Power Skill RefactorUse when an existing skill must be refactored to cut context and ambiguity without losing behavior, safety or fallbacks — 'refatorar a skill', 'reduzir esta SKILL.md', 'revisar skill com métricas' — with before/after metrics, preserved invariants and three review rounds.Votes: 0GitHub stars: 3