docs(skill): require minimal repository-native security fixes

[tdullien1]

Summary

Make automatically generated security patches follow local coding conventions and remain narrowly focused on the vulnerability being fixed.

Changes

• Identify applicable organization-wide and project-specific style guides before editing.
• Match nearby naming, types, control flow, formatting, and error-handling conventions.
• Preserve existing APIs, helper signatures, assertions, and legitimate behavior unless a change is required for security closure.
• Avoid unrelated refactoring, cleanup, renaming, and formatting changes.
• Review the complete candidate patch against its original base while preserving pre-existing user changes.

Testing

• Focused CLI skill-command suite: bun test --timeout 30000 tests-ts/cli-skills.test.ts — 25 passed.
• Bundled skill structural validation — passed.
• Prettier check for the changed skill — passed.
• git diff --check — passed.

Risk and rollout

Instruction-only update to one bundled skill; no runtime APIs, dependencies, or release configuration change. Existing requirements for complete security closure and preserving user-owned changes remain intact.

Public disclosure review

• No customer, partner, prospect, or user identities, data, or identifying details are included.
• No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
• I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.

[mldangelo-oai]

Great! I will trust that this performs better than it did before. Would be cool to eval but not necessary