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.
Simplify Code Without Changing Behavior
Complex code slows reviews, maintenance, and debugging. This skill guides focused refactoring that improves clarity while preserving behavior, errors, side effects, and tests.
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "code-simplification" from https://skillstore.io/skills/addyosmani-code-simplification.md and its manifest at https://skillstore.io/api/skills/addyosmani-code-simplification/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Utilisation de « code-simplification ». A function uses four nested conditionals to validate input, permission, and state.
Résultat attendu:
Recommend ordered guard clauses with one validation per step. Explain that the change should preserve exception types, messages, and successful results.
Utilisation de « code-simplification ». A pull request mixes a new feature with a broad cleanup of nearby modules.
Résultat attendu:
Recommend separating the feature and cleanup into independent changes. Identify unrelated files as scope expansion and request tests for each focused refactor.
Utilisation de « code-simplification ». A helper appears redundant, but its callers and historical purpose are unclear.
Résultat attendu:
Defer removal until callers, tests, project conventions, and history are understood. Record the missing evidence instead of guessing.
All 26 external-command findings are false positives caused by shell-like backticks in Markdown examples and inline code. The hardcoded URL is a documentation reference, and the five reconnaissance findings describe ordinary scope and verification practices; no malicious intent or prompt injection was found.
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
https://skillstore.io/skills/addyosmani-code-simplification/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/addyosmani-code-simplification?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/addyosmani-code-simplification?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-code-simplification/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/addyosmani-code-simplification.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-simplification security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-code-simplification/audits/1@techreport{addyosmani-addyosmani-code-simplification-2026,
author = {addyosmani},
title = {code-simplification security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/addyosmani-code-simplification/audits/1},
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-simplification security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "addyosmani"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/addyosmani-code-simplification/audits/1"
identifiers:
- type: other
value: "skillstore:addyosmani-code-simplification:audit:1"
description: "Skillstore immutable audit report identifier"
Review recently changed code for unnecessary nesting, duplication, and unclear names while keeping the feature behavior unchanged.
Turn a broad readability concern into small refactoring steps, explicit checks, and a focused reviewable diff.
Understand an older module before simplifying it, preserving error paths, side effects, project conventions, and existing tests.
Review this function for readability issues. Identify the smallest behavior-preserving improvements and explain why each one helps.
Inspect this module and its tests. Propose one simplification at a time, describe the preserved behavior, and specify the test to run after each step.
Study the surrounding code and project conventions before reviewing this change. Suggest clarity improvements that match existing naming, error handling, and module patterns.
Analyze this refactoring candidate deeply. Trace callers, side effects, error paths, edge cases, tests, and historical constraints, then produce a staged plan with explicit stop conditions.
Auteur
addyosmaniLicence
MIT
Révision Skillstore
r1
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
Réf
5d5054f8a23586f9b500fece1cb613a9dffc787b
Récence de maintenance
19/09/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
đ 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.
Examiner le code selon cinq axes de qualité
Les modifications de code peuvent dissimuler des problĂšmes de fiabilitĂ©, de sĂ©curitĂ©, dâarchitecture, de lisibilitĂ© et de performances. Cette compĂ©tence applique un processus dâexamen structurĂ© et produit des retours hiĂ©rarchisĂ©s et exploitables.
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.
Harden Applications Against Security Risks
Security reviews can miss trust boundaries and unsafe data flows. This skill supplies threat-modeling prompts, OWASP patterns, and practical review checklists.
Guide TDD avec Rouge-Vert-Refactorisation
par mattpocock
Le travail test-first devient souvent fragile lorsque les équipes testent les éléments internes ou écrivent trop de tests dÚs le départ. Cette skill guide Codex, Claude et Claude Code à travers des cycles rouge-vert-refactorisation axés sur le comportement.
Analyser les modĂšles de code et lâarchitecture
par C0ntr0lledCha0s
Les grands codebases cachent des structures répétées et des choix architecturaux peu clairs. Cette compétence trouve les modÚles, explique leur intention et met en évidence des opportunités pratiques de refactorisation.
Rechercher du code par structure AST
par 0xDarkMatter
Les recherches textuelles passent à cÎté des relations sémantiques et produisent des correspondances parasites. Cette compétence utilise des motifs ast-grep pour localiser des structures de code et préparer des refactorisations ciblées.
Créer une automatisation de tests fiable
par 89jobrien
Les tests faibles ralentissent les livraisons et masquent les rĂ©gressions. Cette compĂ©tence guide la stratĂ©gie de test, le TDD, lâautomatisation, lâexamen de la couverture et les vĂ©rifications web avec Playwright.
Trouver le contexte du code plus rapidement
par 89jobrien
Les développeurs perdent souvent du temps à retracer pourquoi du code existe et ce qui en dépend. Cette skill invite Claude, Codex ou Claude Code à rassembler les connaissances de graphe associées, les appelants, les imports et les tests avant les modifications.
Planifier des tests fiables dans toute votre base de code
par 0xDarkMatter
Cette compĂ©tence aide les Ă©quipes Ă choisir des stratĂ©gies de test, des mocks, des jeux de donnĂ©es, des seuils de couverture et des modĂšles CI sans mĂ©langer les pĂ©rimĂštres de test. Elle fournit Ă Claude, Codex et Claude Code des recommandations structurĂ©es pour les tests unitaires, dâintĂ©gration, de bout en bout, TDD e