aliengiraffe/vigilante-issue-implementation-on-gradle
skills/vigilante-issue-implementation-on-gradle/SKILL.md
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Gradle monorepo.
$ install --global
skillsauthnpx skillsauth add aliengiraffe/vigilante vigilante-issue-implementation-on-gradleInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 5:34 AM82.5s1 file scanned
SKILL.md
- name:
- vigilante-issue-implementation-on-gradle
- description:
- Implement a GitHub issue end-to-end when Vigilante dispatches work for a Gradle monorepo.
Vigilante Gradle Monorepo Issue Implementation
Focus
- Read the prompt for the detected stack, workspace hints, and shared local-service contract before changing code.
- Limit edits and validation to the affected Gradle projects unless broader changes are required.
- If local services are required, call
vigilante-local-service-dependenciesfirst and then use the shareddocker-compose-launchcontract instead of writing ad hoc Compose logic.
Workflow
- Follow the base
vigilante-issue-implementation-on-monorepoworkflow for issue comments, validation, push, and PR creation. - Use
vigilante commitfor all commit-producing operations. Do not usegit commitor GitHub CLI commit flows directly. - Any commit or amend must preserve the user's existing git author, committer, and signing configuration. Commit on behalf of the user and do not overwrite
git configwith a coding-agent identity. - Do not add
Co-authored by:trailers or any other agent attribution for Codex, Claude, Gemini, or similar coding-agent identities. - Use Gradle-native project commands when they exist and match the touched modules.
- Keep service startup scoped to the assigned worktree and only for implementation or test dependencies.
Related Skills
aliengiraffe/vigilante-issue-implementation-on-terraform
testing
VerifiedTrustedCommunity
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Terraform repository with fmt, validate, and secret-safe infrastructure guidance.
27SKILL.mdUpdated Apr 24, 2026
aliengiraffe/vigilante-issue-implementation-on-rust
tools
VerifiedTrustedCommunity
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Rust repository with Cargo, Clippy, fmt, and security guidance.
27SKILL.mdUpdated Apr 24, 2026
aliengiraffe/vigilante-issue-implementation-on-ruby
development
VerifiedTrustedCommunity
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Ruby repository with Bundler, test, lint, and security guidance.
27SKILL.mdUpdated Apr 24, 2026
aliengiraffe/vigilante-local-service-dependencies
testing
VerifiedTrustedCommunity
Prepare local service dependencies for an implementation worktree by preferring repository-native startup flows before falling back to compatible local mechanisms.
23SKILL.mdUpdated Apr 3, 2026