Code Quality

Coding style standards, security guidelines, and accessibility requirements. Use when (1) Writing new code, (2) Reviewing code for style/security, (3) Implem...

Security Scan

The skill is an instruction-only 'code quality' checklist that is internally consistent with its stated purpose; the main issue is that it references local 'references/' files that are not included, which reduces usefulness but is not suspicious or malicious.

Purpose & Capability

The name, description, and runtime instructions align: this is a code-style/security/accessibility checklist. However, the SKILL.md refers to local reference files (references/coding-style.md, references/security-checklist.md, references/accessibility-standards.md) that are not included in the bundle, which is an inconsistency that will make the skill less useful.

Instruction Scope

Instructions stay within the stated scope (coding style, security, accessibility). They explicitly prohibit embedding real credentials and ask for test fixtures. One operational detail to note: the guidance asks for responsive checks 'with notes/screenshots' — screenshots can accidentally expose sensitive data if not redacted; the skill itself does not provide mechanisms for safe capture/redaction.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest-risk installation surface.

Credentials

The skill requests no environment variables, binaries, or credentials. Its requirements are minimal and proportionate to its described functionality.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request persistent or elevated platform privileges.

Assessment

This skill is essentially a checklist and appears safe to add, but consider the following before installing or relying on it: (1) The SKILL.md references 'references/...' files that are not bundled—ask the publisher for those documents or provide your own project-specific references. (2) When following the guidance to include screenshots, ensure screenshots are taken from test accounts and are redacted to remove any PII/credentials. (3) Confirm the style rules (naming, indentation, line length) match your project's conventions before applying them automatically. (4) Because the skill is instruction-only, it cannot itself redact or sanitize content—avoid running it against private repositories or production data until you've verified its behavior. If you want stronger assurance, request the missing reference files and a short example of how the skill is used in a code review workflow.

Code Quality Standards

Coding Style

• Naming: camelCase for vars/functions; PascalCase for classes/types
• Formatting: 4-space indentation; target ≤80 chars (wrap thoughtfully)
• Comments: Meaningful, current; delete stale comments
• Security: Never log secrets/PII; validate inputs; least privilege by default
• Errors/Logs: Explicit error types; structured logs by level; actionable messages

Accessibility & UX Quality

• Favor semantic roles/labels; keyboard nav and focus order must work
• Include responsive checks at 375, 768, 1024, 1440 with notes/screenshots
• Use deterministic test IDs; avoid brittle CSS/XPath

Security & Compliance Guardrails

• No real credentials in code, tests, or screenshots
• Use test accounts/fixtures; redact secrets
• Follow least-privilege and input validation
• Document threat considerations in PR when relevant

Reference Files

See references/coding-style.md for detailed style guide, formatting rules, comment standards.

See references/security-checklist.md for security validation checklist, threat modeling, PII handling.

See references/accessibility-standards.md for WCAG compliance, semantic HTML patterns, keyboard nav testing.