security-review

Scan secrets and vulnerabilities in Nav codebases during pre-commit and pre-PR workflows.

1|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/navikt/watson-sak-frontend --skill security-review-navikt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/navikt/watson-sak-frontend/tree/main/.opencode/skills/security-review
Command: npx skills add https://github.com/navikt/watson-sak-frontend --skill security-review-navikt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents insecure code from entering the main branches by enforcing pre-commit and pre-PR security checks, scanning secrets, vulnerabilities, and Nav-specific compliance.

Core Features & Use Cases

  • Secret and vulnerability scanning for Nav applications during pre-commit and PR workflows.
  • Checks for Nav-specific security requirements and governance.
  • Use Case: before merging changes to a Nav project, ensure no secrets or high-risk CVEs slip in.

Quick Start

Run a security review on the changes in your feature branch before pushing.

Frequently Asked Questions about security-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate secret and vulnerability scanning before merging code?

Automate secret and vulnerability scanning by running pre-commit and pre-PR security checks to prevent risky code from entering main branches. This ensures no secrets or high-risk CVEs slip into your project during development workflows.

What is pre-PR security review and when do I need it?

Pre-PR security review is an automated check that scans code changes for secrets, vulnerabilities, and policy compliance before a pull request is submitted. You need it to enforce security governance and prevent insecure code from entering main branches.

Does this security review enforce Nav-specific compliance requirements?

Yes, the security review checks for Nav-specific security requirements and governance. It applies parameterized checks and policy-compliant governance across CI pipelines specifically for Nav project codebases.

Can I run vulnerability scanning on my feature branch before pushing?

Yes, you can run a security review on the changes in your feature branch before pushing. The automated checks scan for secrets, vulnerabilities, and adherence to Nav-specific security requirements during your development workflow.

What do I need to configure to enforce pre-commit security checks in CI pipelines?

You need scanning tools and configuration to enforce parameterized checks, secrets detection, and policy-compliant governance across CI pipelines. These tools automate security checks at pre-commit and pre-PR stages for Nav applications.

Why should I use automated pre-commit checks instead of manual code review?

Automated pre-commit checks prevent insecure code from entering main branches by consistently scanning secrets, vulnerabilities, and Nav-specific compliance. Manual code review lacks the parameterized scanning and policy governance enforcement needed for reliable security.