Skip to content

chore: add snyk security scan skill #518

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mwbrooks merged 2 commits into from
May 4, 2026
Merged

chore: add snyk security scan skill #518

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d1940c7
chore: add snyk security scan skill
mwbrooks May 1, 2026
6432b78
Merge branch 'main' into mwbrooks-snyk
mwbrooks May 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .claude/settings.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@
"Bash(make build:*)",
"Bash(make lint:*)",
"Bash(make test:*)",
"Bash(snyk:*)",
"Bash(mkdir:*)",
"Bash(tree:*)",
"Bash(vhs:*)",
Expand Down
46 changes: 46 additions & 0 deletions .claude/skills/snyk/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
name: snyk
description: Run Snyk security scans to find dependency vulnerabilities and source code issues. Use for monthly security reviews or when checking for new vulnerabilities.
---

Run a Snyk security scan on this project.

## 1. Check prerequisites

Run `which snyk` to verify Snyk is installed. If not found, tell the user to install it with `brew install snyk` or `npm install -g snyk`.

Run `snyk auth check` or `snyk whoami` to verify authentication. If not authenticated, tell the user to run `! snyk auth` to log in interactively.

## 2. Run `snyk test` (dependency vulnerabilities — primary scan)

Run `snyk test` to scan Go module dependencies for known vulnerabilities.

**This is the most important scan.** Summarize the results:

- Group vulnerabilities by severity: **Critical > High > Medium > Low**
- For each vulnerability, note:
- The affected package and version
- Whether a fix is available (upgrade path exists) or requires waiting on the upstream maintainer
- For fixable issues, propose the specific `go get` upgrade commands
- For unfixable issues, note them as "waiting on upstream" — these are deferred

## 3. Run `snyk code test` (source code analysis — secondary scan)

Run `snyk code test` to scan the project's own Go source code for security issues.

**This scan is optional and secondary.** Summarize the results:

- Group findings by severity
- Identify which issues are simple/quick to fix vs. complex
- Focus on simple fixes that can be resolved quickly

## 4. Present a prioritized action plan

Combine both scan results into a single prioritized plan:

1. **Fix now** — dependency upgrades with available fixes (propose commands)
2. **Fix now** — simple source code issues from `snyk code test`
3. **Defer** — dependency vulnerabilities waiting on upstream fixes
4. **Defer** — complex source code issues that need more investigation

Ask the user which items they'd like to tackle, then help resolve them.
Loading