deps
Check and tidy Go module dependencies. Use after adding/removing imports or before releases.
Best use case
deps is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Check and tidy Go module dependencies. Use after adding/removing imports or before releases.
Teams using deps should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/deps/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How deps Compares
| Feature / Agent | deps | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Check and tidy Go module dependencies. Use after adding/removing imports or before releases.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Dependency Management Check and tidy Go module dependencies to keep go.mod/go.sum clean. ## Usage - `/deps` - Tidy and verify dependencies ## Steps 1. **Tidy modules** ```bash go mod tidy 2>&1 ``` 2. **Verify checksums** ```bash go mod verify 2>&1 ``` 3. **Check for changes** ```bash git diff --stat go.mod go.sum 2>&1 ``` 4. **Report findings** ``` ## Dependency Check ### Changes - [added/removed/changed dependencies] ### Verification - Checksums: OK / issues found ### Summary - go.mod changed: yes/no - go.sum changed: yes/no ``` 5. **If dependencies changed**, show the diff and explain what was added or removed. ## When to Run - After adding new imports - After removing packages or code - Before creating a PR - After resolving merge conflicts in go.mod/go.sum
Related Skills
test
Run Go unit tests. Use after code changes to verify correctness.
security-scan
Run gosec and govulncheck to find security vulnerabilities. Use before releases or after dependency changes.
reindex
Trigger reindexing of a specific WordPress extension. Use to rebuild the search index for a plugin, theme, or core version.
race-check
Run Go race detector to find data races in concurrent code. Use after any change to mutexes, goroutines, or channels.
profile
Run CPU and memory profiling with pprof to identify performance hotspots. Use when investigating high resource usage.
migrate
Create and manage database migrations using goose. Use for schema changes, new tables, or index optimization.
lint
Run golangci-lint and static analysis on Go code. Use before pushing or to check code quality.
integration-test
Run integration tests that require Docker (Postgres, MinIO via testcontainers). Use to validate database and storage behavior.
generate
Run go generate to build templ templates and frontend assets. Use after changing templates or CSS/JS.
coverage
Run tests with coverage analysis and identify untested code paths. Use to find gaps before releases.
check
Run pre-push quality checks (vet + lint + tests with race detector). Use before pushing code.
benchmark
Run Go benchmarks and compare results to detect performance regressions. Use before and after performance-related changes.