code-review-and-quality
78Review 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.
Test Browser Experiences with Chrome DevTools
Browser bugs can hide behind static code and incomplete unit tests. This skill uses Chrome DevTools MCP to inspect live behavior and verify fixes with runtime evidence.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "browser-testing-with-devtools" from https://skillstore.io/skills/addyosmani-browser-testing-with-devtools.md and its manifest at https://skillstore.io/api/skills/addyosmani-browser-testing-with-devtools/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 "browser-testing-with-devtools". Inspect the local task page after completing one task.
Expected outcome:
Using "browser-testing-with-devtools". Investigate a button that looks correct but does not respond.
Expected outcome:
The button is present in the DOM, but its click handler throws a runtime error. The error appears in the console before any network request is sent.
Using "browser-testing-with-devtools". Review a page before release.
Expected outcome:
All 30 static findings are false positives in the audited documentation. The command, filesystem, network, screenshot, reconnaissance, and prompt-injection matches describe configuration, safe testing boundaries, or local verification steps rather than malicious behavior.
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-browser-testing-with-devtools/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/addyosmani-browser-testing-with-devtools?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/addyosmani-browser-testing-with-devtools?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-browser-testing-with-devtools/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/addyosmani-browser-testing-with-devtools.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). browser-testing-with-devtools security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-browser-testing-with-devtools/audits/2@techreport{addyosmani-addyosmani-browser-testing-with-devtools-2026,
author = {addyosmani},
title = {browser-testing-with-devtools security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/addyosmani-browser-testing-with-devtools/audits/2},
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: "browser-testing-with-devtools security audit report (audit version 2)"
version: "unspecified"
type: report
authors:
- name: "addyosmani"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/addyosmani-browser-testing-with-devtools/audits/2"
identifiers:
- type: other
value: "skillstore:addyosmani-browser-testing-with-devtools:audit:2"
description: "Skillstore immutable audit report identifier"
Reproduce a layout or interaction bug, inspect the DOM and styles, capture evidence, and verify the implemented fix.
Exercise a browser workflow and confirm request methods, payloads, responses, and console behavior against expected results.
Check accessibility structure, visual output, performance signals, and browser errors before shipping a user-facing change.
Open the local page I provide. Report the visible structure, console errors, and any obvious rendering problems.
Reproduce the reported UI issue, inspect the affected element and computed styles, then verify the fix with a fresh screenshot.
Run the specified user flow. Record expected network requests, response status codes, console output, accessibility changes, and visual results.
Capture a performance trace before and after the change. Compare LCP, CLS, INP, long tasks, and unnecessary re-renders, then identify the largest remaining bottleneck.
Author
addyosmaniLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
5d5054f8a23586f9b500fece1cb613a9dffc787b
Maintenance freshness
9/19/2026
Usage
1 downloads ยท 0 views
File structure
๐ SKILL.md
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.
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.
Debug Errors and Root Causes
by 89jobrien
Errors and incidents are hard to triage when evidence is spread across logs, stack traces, and services. This skill structures diagnosis, parses logs, identifies patterns, and guides minimal fixes.
Find Code Context Faster
by 89jobrien
Developers often lose time tracing why code exists and what depends on it. This skill prompts Claude, Codex, or Claude Code to gather related graph knowledge, callers, imports, and tests before changes.
Improve SwiftUI Code with Expert Guidance
by avdlee
SwiftUI projects can accumulate state, layout, accessibility, and performance problems. This skill provides focused review guidance and optional Instruments trace analysis to identify practical improvements.
Design Reliable Tools for AI Agents
by Asmayaseen
Ambiguous tools cause incorrect calls, wasted context, and poor recovery from errors. This skill provides practical patterns for clear descriptions, schemas, responses, and testing.
Debug Technical Failures Systematically
by Asmayaseen
Quick fixes often hide the real cause and create regressions. This skill structures investigation, hypothesis testing, implementation, and verification around collected evidence.
Diagnose Context Degradation in AI Agents
by ChakshuGautam
Long conversations and large prompts can make AI agents lose important information or follow conflicting context. This skill helps Claude, Codex, and Claude Code identify degradation patterns and choose mitigation strategies.