Vigilante issue implementation on nx

Implement a GitHub issue end-to-end when Vigilante dispatches work for an Nx monorepo.From its SKILL.md

Install

npx -y skills add aliengiraffe/vigilante --skill vigilante-issue-implementation-on-nx

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

runs commandsInstructs the agent to run 2 commands, including `vigilante-local-service-dependencies` and 1 more.

1.4 KB, 268 tokens by cl100k_base, as published. Nobody here has run it

Read the prompt for the detected stack, workspace hints, and shared local-service contract before changing code.
Limit edits and validation to the affected Nx apps or libs unless broader changes are required.
If local services are required, call vigilante-local-service-dependencies first and then use the shared docker-compose-launch contract instead of writing ad hoc Compose logic.

Follow the base 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).
Use vigilante commit for all commit-producing operations. Do not use git commit or 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 config with 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 Nx-native workspace commands when they exist and match the touched projects.
Keep service startup scoped to the assigned worktree and only for implementation or test dependencies.

326 B alongside SKILL.md