agentsclimarketplace
Sign in

Policyengine github agent

Skill PolicyEngine/policyengine-claude/skills/policyengine-github-agent

Working with the PolicyEngine GitHub agent bot on issues and PRs — how it is invoked and the hard rule that keeps it from looping. Load before replying to, or posting as, the bot. Triggers: "@policyengine bot", "GitHub agent", "policyengine-github-agent", "bot doom loop", "bot mentioned itself", "who can invoke the bot", "core-developers team".From its SKILL.md

Install
npx -y skills add PolicyEngine/policyengine-claude --skill policyengine-github-agent

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

SKILL.md

2.4 KB, as published. Nobody here has run it

PolicyEngine GitHub agent

For Users

The PolicyEngine GitHub agent is an automated bot that can be invoked on GitHub issues and pull requests using @policyengine mentions. It helps with code reviews, bug fixes, and implementing features across PolicyEngine repositories.

For Contributors

Critical: Avoiding Doom Loops

NEVER use '@policyengine' or '@policyengine-auto' in bot responses. These mentions trigger the bot and create infinite loops where the bot repeatedly responds to itself.

Why This Matters

When the bot posts a comment containing @policyengine, GitHub notifies the bot account, which triggers another invocation. This creates a chain reaction of bot responses that can generate dozens or hundreds of comments before being stopped. See PR #22 for a real example of this issue.

Safe Alternatives

Instead of mentioning the bot directly:

❌ Don't do this:

  • "Thanks @policyengine for the suggestion!"
  • "I've addressed @policyengine's feedback"
  • "cc @policyengine-auto"

✅ Do this instead:

  • "I've implemented the suggested changes"
  • "The feedback has been addressed"
  • "Updated based on the review comments"
  • Simply refer to "the bot" or "the agent" without the @ mention

Bot Invocation

The bot can only be invoked by members of the PolicyEngine/core-developers team. Non-members will receive a permission error.

Response Style

When the bot responds to issues or PRs:

  • Keep responses concise and actionable
  • Focus on the technical task at hand
  • Avoid unnecessary pleasantries or acknowledgments
  • Never include @ mentions of the bot usernames

Resources

Keep looking

Skills are one crate of 627,801. 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.