code-quality-workflow
Use when assessing or improving code quality, maintainability, performance, or security hygiene - provides workflows for analysis, code review, and systematic improvements with validation steps.
Works with
--- name: code-quality-workflow description: Use when assessing or improving code quality, maintainability, performance, or security hygiene - provides workflows for analysis, code review, and systematic improvements with validation steps. license: MIT --- # Code Quality Workflow ## Overview Standardize how to analyze, review, and improve code quality. This skill centralizes quality assessment, code review practices, and systematic improvements with validation gates. ## When to Use - Quality assessment or code analysis requests - Code review (PRs, refactors, pre-merge checks) - Maintainability or performance improvements - Security hygiene improvements (non-audit level) Avoid when: - A full security audit is required (use security-specific skills) - The task is purely dependency or artifact cleanup (use repo-cleanup) ## Quick Reference | Task | Load reference | | --- | --- | | Code analysis | `skills/code-quality-workflow/references/analyze-code.md` | | Code review | `skills/code-quality-workflow/references/code-review.md` | | Systematic improvements | `skills/code-quality-workflow/references/quality-improve.md` | ## Workflow 1. Select the mode: analyze, review, or improve. 2. Load the matching reference file for the expected structure. 3. Inspect code and identify findings or opportunities. 4. Apply changes (if improving) with safety validation. 5. Verify with tests or lint as appropriate. 6. Report findings, fixes, and follow-ups. ## Output - Findings or improvements summary - Validation evidence or recommended checks - Follow-up backlog items if needed ## Common Mistakes - Skipping severity prioritization - Mixing review and improvement without sign-off - Applying fixes without baseline tests - Overlapping with full security audit scopes
More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
Use 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 implementation
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.

