security-best-practices

Security best practices are identified by matching your project's languages and frameworks against official references, then producing a structured report with risk severity, evidence, and concrete patches aligned with CI/CD workflows.

A secure-by-default remediation plan provides concrete, minimal patches and configuration changes to fix vulnerabilities, prioritizing guidance based on risk severity to ensure production-safety requirements are met during code reviews.

Generate security best-practices metadata by loading and validating frontmatter, references, and operational instructions to produce a structured report that includes evidence, risk severity, and remediation guidance for each valid skill unit found.

Yes, you can integrate security best practices into CI/CD workflows to generate secure-by-default code and prioritized remediation plans based on repository content, ensuring continuous risk assessment and compliance alignment.

Yes, the security best-practices skill operates without external dependencies, relying solely on its internal references component to consolidate official guidance and generate structured metadata reports for vulnerability remediation.

The best way to consolidate official security guidance is to centralize discovery of language and framework-specific references, enabling consistent onboarding and review workflows while producing structured remediation metadata for each valid skill unit.