Security audit
Security checks for vulnerabilities and agentic risk
This skill is a scoped refactoring guide for frontend inheritance changes and does not show hidden execution, credential access, persistence, or unrelated data handling.
Install this as a normal refactoring aid. Review proposed code changes before applying them, especially when public contracts, serialization, lifecycle behavior, or subtype identity may change.
Referenced artifact was not completely inspected
1. Confirm the selected technique and its preconditions in [Inheritance Refactorings](references/inheritance-refactorings.md).
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
- ID: `fec-refactoring-inheritance`
- Category: `review-quality`
- Version: `2.9.0`
- Source: `skills/fec-refactoring-inheritance/SKILL.md`
## Description
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
The family reference contains 11 canonical techniques with intent, signals, avoid conditions, mechanics, preservation checkpoints, smell links, composition hints, JavaScript/TypeScript notes, React/Vue notes, adaptation guidance, and original frontend examples.
## Common Mistakes
- Choosing a technique by name without checking its preconditions.
- Combining several structural intentions in one diff.
- Assuming a classical class-based form is mandatory in modern frontend code.
- Treating passing tests as proof when the relevant behavior is not covered.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
The family reference contains 11 canonical techniques with intent, signals, avoid conditions, mechanics, preservation checkpoints, smell links, composition hints, JavaScript/TypeScript notes, React/Vue notes, adaptation guidance, and original frontend examples.
## Common Mistakes
- Choosing a technique by name without checking its preconditions.
- Combining several structural intentions in one diff.
- Assuming a classical class-based form is mandatory in modern frontend code.
- Treating passing tests as proof when the relevant behavior is not covered.
This is a manifest file, so vague trigger analysis applies. The description says to use the skill when refactoring 'focuses on legacy OO hierarchies' and related topics, but it does not define explicit trigger phrases, exclusions, or negative examples, which could make invocation boundaries somewhat ambiguous in overlapping refactoring contexts.
No suspicious patterns detected.