القائمة
Generate SECURITY.md for vulnerability reporting. Use when creating or updating security policies with supported versions and reporting instructions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | docs-generate-security |
| description | Generate SECURITY.md for vulnerability reporting. Use when creating or updating security policies with supported versions and reporting instructions. |
| allowed-tools | Read, Glob, Edit, Write |
| context | fork |
| agent | user-docs |
Generates a SECURITY.md file with supported versions and vulnerability reporting instructions.
SECURITY.md should be clear and actionable.
A good SECURITY.md tells security researchers:
Keep it simple - most projects only support the latest version.
This skill generates SECURITY.md by:
Generate SECURITY.md:
/design-docs:docs-generate-security
With custom security contact:
/design-docs:docs-generate-security --email=security@example.com
Preview without writing:
/design-docs:docs-generate-security --dry-run
--email: Custom security contact email (default: from package.json author)--dry-run: Preview output without writingFrom package.json:
version field → Current published version0.0.0 or pre-release → "Latest" onlyFrom changesets (if enabled):
.changeset/ directory existsVersion support policy:
| Scenario | Supported Versions |
|---|---|
| Stable (≥1.0.0) | Current major only |
| Pre-release (<1.0.0) | Latest only |
| Monorepo | Per-package or "Latest" |
From package.json:
author.email → Security contactrepository.url → For GitHub security advisories linkFallback: Prompt for security email if not found.
Standard sections:
Write to repository root as SECURITY.md.
Load these files for detailed guidance:
instructions.md - Step-by-step implementationtemplates/security.template.md - Output templateA generated SECURITY.md is successful when:
package.json for version and contact info.changeset/ for pending versionsSECURITY.mddesign-docs:user-docs agent for generation/design-docs:user-docs-create-readme - Generate package README/design-docs:docs-generate-contributing - Generate CONTRIBUTING.mdGenerate cross-reference graph showing relationships between design documents. Use when visualizing doc dependencies, finding related docs, or understanding documentation structure.
Validate design doc structure and frontmatter. Use when checking design docs for compliance, ensuring proper formatting, or verifying metadata before commits.
Comprehensive quality audit for CLAUDE.md context files. Use when performing thorough quality checks, preparing for releases, ensuring context efficiency, or verifying token optimization.
Style rules for LLM context files (CLAUDE.md, AGENTS.md and their .local variants). Fires automatically when these files are opened. Enforces on-demand loading patterns, proper @-reference syntax and lean context structure.
Split large CLAUDE.md into child files. Use when context files exceed word limits, are too verbose, or cover multiple distinct topics that should be separate.
Validate CLAUDE.md structure, formatting, and quality. Use when checking context files for compliance, ensuring proper structure, or verifying before commits.