skills.rest
decocms
decocmsOFFICIAL
Explore all skills by this author →
Website𝕏@deco_cmsGitHub

review

Review staged git changes for hardcoded text, CSS, unused files, and security issues.

13|2|Updated Feb 24, 2026
Search Tags:#git#security#css#review#code-quality#staged-changes
One-click install
npx skills add https://github.com/decocms/storefront-skills --skill review-decocms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/decocms/storefront-skills/tree/main/.claude-deco/skills/review
Command: npx skills add https://github.com/decocms/storefront-skills --skill review-decocms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review staged changes before publishing to identify hardcoded text, CSS issues, unused files, and security concerns.

Core Features & Use Cases

  • Hardcoded Text/Content checks: Ensure user-facing text and configuration are editable.
  • Hardcoded CSS: Flag raw CSS values and enforce design tokens.
  • Unused Components/Files: Detect dead code and orphaned assets.
  • Security Issues: Flag secrets, exposed tokens, or credentials in code or configs.
  • Loaders: Validate loaders for error handling and caching.
  • Sections: Ensure sections export LoadingFallback components and proper prop types.
  • Breaking Changes: Warn on renames/removals that could break pages reliant on shared components.

Quick Start

Run the review workflow on your current git changes to detect hardcoded content, CSS issues, unused files, and security concerns.

Frequently Asked Questions about review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check staged git changes for hardcoded text and security issues?▼

To review staged git changes for hardcoded text and security issues, run a pre-publish review workflow that flags non-configurable content, exposed credentials, and raw CSS values to ensure safe releases.

What is the best way to detect unused files and dead code before publishing?▼

Detecting unused files and dead code before publishing involves scoping checks against your codebase to identify orphaned assets and unused components, documenting actionable findings for remediation.

How does a code review check for hardcoded CSS values and enforce design tokens?▼

A code review checks for hardcoded CSS values by scanning staged changes to flag raw values, enforcing the use of design tokens to maintain styling consistency and maintainability.

Can I validate loaders and section components for error handling during a code review?▼

Yes, you can validate loaders and section components during a code review by checking that loaders implement proper error handling and caching, and sections export required LoadingFallback components.

How do I warn about potential breaking changes across shared components in staged changes?▼

To warn about potential breaking changes in staged changes, review renames and removals across the codebase to prevent breaking pages reliant on shared components, documenting warnings for remediation.

Related Skills

Explore More Software Engineering Skills→
i-standard1i-standard1
6

update-docs

Propagate git-tracked code changes into design docs and OpenAPI specs.

Official
Advanced
chtughachtugha

security-review

Identify security vulnerabilities in code changes and pull requests using OWASP Top 10 standards.

Community
Advanced
oioio-spaceoioio-space

secret-guard

Scan staged Git diffs for credentials, PII, and sensitive data.

Community
Advanced
LayerDynamicsLayerDynamics

diff-review

Review current git diff changes for bugs, security issues, and style inconsistencies.

Community
Intermediate