interview-me
78Clarify User Intent Before You Build
Underspecified requests cause teams to build the wrong outcome and discover misalignment late. This skill runs a focused, one-question interview that turns ambiguity into confirmed intent.
Review Code Across Five Quality Axes
Code reviews often miss risks when they focus only on tests or style. This skill guides a consistent review of correctness, readability, architecture, security, and performance.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "code-review-and-quality" from https://skillstore.io/skills/addyosmani-code-review-and-quality.md and its manifest at https://skillstore.io/api/skills/addyosmani-code-review-and-quality/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "code-review-and-quality". Review a feature change that adds a list endpoint and updates its tests.
Expected outcome:
Using "code-review-and-quality". Review a dependency upgrade that changes the lockfile.
Expected outcome:
Review the changelog and lockfile diff, isolate the package change, run the full test suite, and verify that transitive updates are expected.
Using "code-review-and-quality". Review an AI-generated refactor with passing tests.
Expected outcome:
All 37 static findings are false positives in documentation-only Markdown. The matches are inline backticks, fenced examples, relative links, or ordinary checklist language; no executable behavior, secret access, network activity, or prompt injection was found in SKILL.md.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/addyosmani-code-review-and-quality/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/addyosmani-code-review-and-quality?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/addyosmani-code-review-and-quality?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-code-review-and-quality/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/addyosmani-code-review-and-quality.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>addyosmani. (2026). code-review-and-quality security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-code-review-and-quality/audits/4@techreport{addyosmani-addyosmani-code-review-and-quality-2026,
author = {addyosmani},
title = {code-review-and-quality security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/addyosmani-code-review-and-quality/audits/4},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "code-review-and-quality security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "addyosmani"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/addyosmani-code-review-and-quality/audits/4"
identifiers:
- type: other
value: "skillstore:addyosmani-code-review-and-quality:audit:4"
description: "Skillstore immutable audit report identifier"
Evaluate a proposed change before merge with prioritized findings across correctness, design, security, and performance.
Inspect code produced by an agent for hidden assumptions, weak tests, unsafe patterns, and unnecessary complexity.
Separate structural improvements from feature work and identify simpler designs before implementation begins.
Review this change for correctness, readability, architecture, security, and performance. List the most important issues first.
Review this change and its tests. Identify missing edge cases, weak assertions, error paths, and regressions the tests would not catch.
Assess this change for coupling, duplication, misplaced responsibilities, abstraction debt, and complexity that was relocated rather than removed.
Perform a release-readiness review. Prioritize correctness and security risks, inspect dependency changes, assess verification evidence, and propose concrete remedies.
Author
addyosmaniLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
5d5054f8a23586f9b500fece1cb613a9dffc787b
Maintenance freshness
9/19/2026
Usage
12 downloads ยท 0 views
File structure
๐ SKILL.md
Clarify User Intent Before You Build
Underspecified requests cause teams to build the wrong outcome and discover misalignment late. This skill runs a focused, one-question interview that turns ambiguity into confirmed intent.
Plan Work Into Verifiable Tasks
Large or vague software work can hide dependencies, missing acceptance criteria, and verification gaps. This skill converts a specification into ordered task slices with checkpoints, scope guidance, and clear completion conditions.
Document Decisions and Architecture Clearly
Teams lose context when important technical decisions remain in chat, code comments, or individual memory. This skill turns architectural reasoning, API guidance, project instructions, and release changes into structured documentation.
Build Accessible, Production-Ready Frontends
Frontend work can become inconsistent, inaccessible, or difficult to maintain. This skill guides component architecture, responsive layouts, state handling, and polished user experiences.
Debug Errors with a Root-Cause Workflow
Debugging failures by guesswork wastes time and can hide the real cause. This skill provides a repeatable process for reproducing, isolating, fixing, and verifying problems.
Structure Better Context for Coding Agents
Coding agents lose accuracy when context is incomplete, stale, or excessive. This skill provides practical structures for focused sessions, durable rules, and reliable handoffs.
Teach Code by Building Apps
by Emz1998
Learning code can feel abstract when examples are disconnected from real projects. This skill teaches concepts while building working applications step by step.
Route CC-DevFlow Workflows
by Dimon94
Teams lose time choosing the next CC-DevFlow command during complex delivery work. This skill maps project status, phase gates, and user intent to the right Claude, Codex, or Claude Code workflow.
Trace Requirements to Verified Delivery
by solohic
Teams can lose requirements when agent-skill work moves from planning to implementation and review. This skill keeps requirements, acceptance evidence, review state, and completion claims connected through a clear traceability process.
Trace Requirements Across Superpowers Workflows
by solohic
Development teams can lose requirement evidence across planning, implementation, review, and release. This skill adds RVTF traceability while preserving Superpowers task boundaries and control.
Review Code for Clean Code Issues
by hylarucoder
Code quality issues slow reviews and make changes risky. This skill finds Clean Code problems and gives prioritized refactoring guidance.
Improve Evidence-Based Reasoning
by 89jobrien
Complex reviews and decisions often fail when claims outrun evidence. This skill provides verification workflows, hypothesis testing, and self-correction prompts.