Code Review & Quality

Code review, refactoring, debugging, maintainability, and engineering quality

skills in category: 14,948
pages available: 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 browser

Browse code review & quality skills

Showing 697–720 of 14,948 skills

Creating Semantic Keyword MapsASemantic keyword mapping for pillar content: group keywords that share search results and intent, then assign each group to exactly one page.code-qualityrustgoVotes: 0GitHub stars: 2
Creating Kanban Pull PoliciesAKanban pull policies define entry and exit criteria for each column, so everyone knows when work may be pulled forward, by whom, and in what order.code-qualitygogitVotes: 0GitHub stars: 2
Crafting Actionable Feedback PromptsAWrite start stop continue questions and prompts with a clear scope and time frame, so each column draws specific, actionable answers.code-qualityrustgoVotes: 0GitHub stars: 2
Coaching Agile Team AdoptionAAgile coaching for teams in adoption: map how they work today, add one practice at a time with their consent, and hand the process over to them.code-qualityrustgoVotes: 0GitHub stars: 2
Categorizing Feedback Into 4lsASort team feedback into the 4Ls categories, tell Liked, Learned, Lacked and Longed For apart, and resolve notes that fit more than one.code-qualityrustgoVotes: 0GitHub stars: 2
Categorizing And Prioritizing Feedback ItemsACategorize and prioritize retrospective feedback: cluster Start, Stop and Continue items into themes, dot vote, and cut the list to a few owned actions.code-qualitygoperformanceVotes: 0GitHub stars: 2
Building Sprint Retrospective TemplatesABuild a reusable retrospective template that maps activities, timings and facilitator cues to the five phases, so anyone can run a solid sprint retro.code-qualitygogitVotes: 0GitHub stars: 2
Building Interdisciplinary Fde SkillsetsAFDE skill development: assess and train the engineering, data, domain and communication skills a forward deployed engineer needs on site.code-qualitygodebuggingVotes: 0GitHub stars: 2
Applying Moscow To Project RequirementsAHow to prioritize requirements with MoSCoW inside a project or software backlog, so each one carries a category from discovery to delivery.code-qualitygotestingVotes: 0GitHub stars: 2
Thermo Nuclear Code Quality ReviewARun an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.code-qualitygoapiVotes: 0GitHub stars: 2
Systematic DebuggingAUse when encountering any bug, test failure, or unexpected behavior, before proposing fixescode-qualitydebuggingVotes: 0GitHub stars: 2
Self Healing Skills Thread Driven Skill ImprovementAAnalyze any conversation thread for skill gaps and improvement opportunities. When a thread involves friction, trial-and-error, or discovery that could have been avoided with better skill documentation, this skill provides the protocol to identify whether to UPDATE an existing skill, CREATE a new one, or take NO ACTION. Makes the self-improving organizational harness systematic: every conversation with friction becomes a captured knowledge opportunity.code-qualitygoexpressVotes: 0GitHub stars: 2
Requesting Code ReviewAUse when completing tasks, implementing major features, or before merging to verify work meets requirementscode-qualitycode-reviewVotes: 0GitHub stars: 2
Receiving Code ReviewAUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationcode-qualitygocode-reviewVotes: 0GitHub stars: 2
Pr WalkthroughAProduce a reviewer's orientation guide for a large or foundational pull request — a structured walkthrough that explains the mental model, traces the data/code flow, recommends a reading order, and tells the reviewer how to see and test the change locally. NOT a code review and does NOT produce inline review comments. Use when the user says things like \\\"explain this PR to me\\\", \\\"walk me through this PR\\\", \\\"I was asked to review this huge PR\\\", \\\"help me understand this PR\\\"...code-qualitygobashVotes: 0GitHub stars: 2
People First Pr DescriptionsAWrite and update pull-request titles and descriptions for technical work. Use whenever creating, revising, or reviewing a PR body, release-style PR summary, or reviewer-facing change explanation—even if the user only says “open a PR,” “update the PR,” “make this understandable,” or provides technical notes. Put people, user outcomes, and why first; move implementation detail and validation after the plain-language explanation.code-qualitygoapiVotes: 0GitHub stars: 2
Nestjs Best PracticesANestJS best practices and architecture patterns aligned with the Hamster Studio stack (nestjs-zod, Supabase, Vitest, BullMQ). Use when writing, reviewing, or refactoring NestJS code. Complements the hamster-nest-api skill which covers project-specific templates.code-qualityrefactoringapiVotes: 0GitHub stars: 2
Mermaid DiagramsABest practices for when to create Mermaid diagrams and how to write good ones — layout direction, readability, shape choice, and anti-patterns. Use when writing or reviewing blueprints, initiatives, or briefs that need visual structure, when deciding whether a diagram is the right format, or when a Mermaid diagram is already in a doc and needs review.code-qualitygonodeVotes: 0GitHub stars: 2
Measure BindingAGuides binding OGSM measures to external platforms (PostHog, Google Search Console). Enforces leading vs lagging tagging, validates the bound event/property exists before claiming live sync, and prevents stale bindings from producing stale numbers. Use when binding a measure to PostHog or Google Search Console, setting up live sync for a measure, or connecting a goal metric to an external platform.code-qualitygodebuggingVotes: 0GitHub stars: 2
Karpathy GuidelinesABehavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.code-qualitygorefactoringVotes: 0GitHub stars: 2
Hamster InstrumentationAPlan-time observability for new features in Hamster Studio. Use PROACTIVELY during plan/brief generation, feature scoping, architectural design, or anytime a new endpoint, server action, BullMQ job, page route, or user-facing surface is being designed. Forces every plan to declare PostHog events, user/account properties, group context, feature flags, session-replay/PII posture, and trace correlation BEFORE code is written. Complements `hamster-analytics` (the implementation API) by making ins...code-qualitygonextjsVotes: 0GitHub stars: 2
Gitnexus GuideAUse when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \\\"What GitNexus tools are available?\\\", \\\"How do I use GitNexus?\\\"code-qualitygonodeVotes: 0GitHub stars: 2
Git Branch SafetyACreate and publish safe feature branches and pull requests, including Hamster brief-aware branch names and PR links. Use for branch creation, any git commit/push, PR creation, workflow dispatch, or CI debugging.code-qualitygobashVotes: 0GitHub stars: 2
Detecting And Flagging Blueprints For RefreshAOn brief.status = \"approved\":code-qualitygoVotes: 0GitHub stars: 2