Menu
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Gradle monorepo.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Help a human author write an implementation-ready GitHub issue that Vigilante can execute reliably.
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Bazel-based monorepo. Use the provided worktree, respect repository instructions, comment on the issue as work progresses, and report failures back to GitHub.
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Bazel monorepo.
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Docker-focused repository with Dockerfile best practices, image hardening, and secret-safe build guidance.
Implement a GitHub issue end-to-end when Vigilante dispatches work for a .NET/C# repository with analyzer, test, and security guidance.
Implement a GitHub issue end-to-end when Vigilante dispatches work for a repository with GitHub Actions workflows, applying workflow hardening, pinned actions, and secret-safe automation practices.
| name | vigilante-issue-implementation-on-gradle |
| description | Implement a GitHub issue end-to-end when Vigilante dispatches work for a Gradle monorepo. |
vigilante-local-service-dependencies first and then use the shared docker-compose-launch contract instead of writing ad hoc Compose logic.vigilante-issue-implementation-on-monorepo workflow for issue comments, validation, push, and PR creation, including stacked base-branch detection (Base branch: directive in the issue body).vigilante commit for all commit-producing operations. Do not use git commit or GitHub CLI commit flows directly.git config with a coding-agent identity.Co-authored by: trailers or any other agent attribution for Codex, Claude, Gemini, or similar coding-agent identities.