agentsclimarketplace

Vigilante issue implementation on rush

Skill aliengiraffe/vigilante/skills/vigilante-issue-implementation-on-rush

Vigilante is a sandbox-first orchestration layer for coding agents. It isolates every task in a git worktree, enforces strict credential scoping, and gives you full audit logs — so your agents can't burn down production.

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

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

What its author says it does

Copied from the file, not written here

Implement a GitHub issue end-to-end when Vigilante dispatches work for a Rush monorepo.

SKILL.md

1.4 KB, as published. Nobody here has run it

Vigilante Rush 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 Rush projects 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.

Workflow

  • 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 Rush-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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.