security

Identify security risks in code changes via threat modeling, secret checks, and dependency audits.

3|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hcross/crewrig --skill security-hcross
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/hcross/crewrig/tree/main/.gemini/skills/security
Command: npx skills add https://github.com/hcross/crewrig --skill security-hcross

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security reviews for changes, threat modeling, secret hygiene, and dependency audits are automated to reduce risk and speed up shipping.

Core Features & Use Cases

  • Threat modeling on diffs
  • Dependency audit and licensing checks
  • Secret hygiene checks and credential handling
  • Code review with a security lens and actionable findings
  • Use Case: When a PR touches authentication, secrets, or cryptography, run a security pass and surface fixes.

Quick Start

Analyze the latest change set for security implications and output prioritized fixes.

Frequently Asked Questions about security

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

FAQPage Schema
How do I automate security reviews for code changes in a PR?

You can automate security reviews on PRs by applying threat modeling, secret hygiene checks, and dependency audits directly to code changes. This generates deterministic checks, traceable findings, and actionable remediation guidance for CI review workflows.

What does threat modeling on a diff actually check for?

Threat modeling on a diff checks for security risks introduced by code changes across authentication, authorization, secrets handling, cryptography, input parsing, deserialization, and network calls. It outputs prioritized fixes to reduce risk and speed up shipping.

Can I use this for dependency audits and secret hygiene checks?

Yes, you can use this for dependency audits and secret hygiene checks. It evaluates credential handling and dependency upgrades introduced by code changes, providing traceable findings and actionable remediation guidance.

Does automated code review work with authentication and cryptography changes?

Automated code review works with authentication and cryptography changes by applying a security lens to the diff. It identifies security risks introduced by these specific code changes and outputs prioritized fixes suitable for integration into CI workflows.

How do I analyze the latest change set for security implications?

Analyze the latest change set for security implications by running threat modeling, secret hygiene checks, and dependency audits on the diff. This outputs prioritized fixes and actionable remediation guidance across authentication, authorization, and network calls.

What is the best way to surface security fixes during a pull request review?

The best way to surface security fixes during a pull request review is to run an automated security pass on the diff. This applies deterministic checks to input parsing, deserialization, and cryptography changes, outputting traceable findings and prioritized remediation guidance.