Open-source skills for designing and reviewing software with AI agents
Python agent-skillsai-agentsantigravityclaude-codeclaude-code-pluginclaude-skillscodexcodex-plugincoding-agentscontext-engineeringdeveloper-toolsgeminillmmulti-agentprompt-engineeringspec-driven-development
Agent Guidelines for Elephant-Goldfish Model (EGM)
You are assisting development in the EGM repository.
Contribution Boundaries
- No Autonomous PRs: You must never automatically open a pull request without explicit human review, testing, and approval.
- No Design Docs for Bug Fixes: Never create files in
docs/designs/for aBug Fix / Minor Patch. A new design doc belongs in the Stage 1 PR of theFeature / Architectural Changetrack. - Triage Taxonomy: Ensure the human operator selects the appropriate track in
.github/PULL_REQUEST_TEMPLATE.md:Bug Fix / Minor Patch(non-test diff<= 100lines and< 3core files inskills/oragents/; no design doc required, but please update an existing design if appropriate).Feature / Architectural Change — Stage 1: Design Doc PR(requires an aligned issue withdesign-ready, usesRefs #<issue>, and addsdocs/designs/<name>.md+ updatesdocs/designs/README.md).Feature / Architectural Change — Stage 2: Implementation PR(requires an aligned issue withpr-readyand a mergeddocs/designs/<name>.md).
- No Artificial PR Splitting: Never split a cohesive feature or refactoring across multiple smaller pull requests to evade the 100-line scope threshold.
- PR Description Template: Every pull request description must be the filled-in
.github/PULL_REQUEST_TEMPLATE.md.gh pr create --bodyskips the template, so copy it from the file. The human author ticks the Accountability box. - Clear Change Summary: In every pull request, explicitly list all key changes
made and why. For feature proposals, define clear in-scope Goals and out-of-scope
Non-Goals in the checked-in EGM design document (
docs/designs/<name>.md).