Skip to content

Comments

Add AGENTS.md and /implement skill#1114

Open
Twinsen81 wants to merge 3 commits intotrunkfrom
add-agents-md-skill
Open

Add AGENTS.md and /implement skill#1114
Twinsen81 wants to merge 3 commits intotrunkfrom
add-agents-md-skill

Conversation

@Twinsen81
Copy link
Contributor

@Twinsen81 Twinsen81 commented Feb 20, 2026

Maintenance

Adds agent guidance files and a unified /implement skill for coding agents working in this repository.

Files added:

  • AGENTS.md — Repository architecture overview, module structure, code navigation, build/test commands, common crash patterns
  • CLAUDE.md — Symlink to AGENTS.md
  • .agents/skills/implement/SKILL.md — End-to-end implementation workflow (plan -> implement -> verify -> commit -> draft PR)
  • .claude/skills — Symlink to .agents/skills

Test

  • Check out the add-agents-md-skill branch
  • Open it in an agentic IDE or CLI
  • Ask the agent to implement a small feature. For example:
Implement a feature: the redacted action changes the background color to red and crosses out the selected text. Add a corresponding button to the toolbar. Create a new branch off this one for this feature.
  • Verify the agent:
    • Presents an implementation plan for approval
    • Implements, verifies, and waits for your approval
    • Commits and creates a draft PR
  • Delete the draft PR

- AGENTS.md with repo architecture, build commands, code navigation
- CLAUDE.md symlink to AGENTS.md
- /implement skill: plan, implement, verify, commit, draft PR workflow
- .claude/skills symlink to .agents/skills
- Agent should write tests for new/changed logic when feasible
- Skip and notify developer when effort would be disproportionate
@Twinsen81 Twinsen81 force-pushed the add-agents-md-skill branch 2 times, most recently from 46cf52a to 6cc4b6c Compare February 20, 2026 12:33
@Twinsen81 Twinsen81 requested a review from zwarm February 20, 2026 13:04
@Twinsen81 Twinsen81 marked this pull request as ready for review February 20, 2026 13:04
@zwarm zwarm self-assigned this Feb 20, 2026
Copy link
Contributor

@zwarm zwarm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Twinsen81 - All looks good. It followed along with the skill. I have suggested a few changes, but none are required. Looks like CI is failing though.


| Skill | Trigger phrases |
|-------------|------------------------------------------------------------------------------------------------------|
| `implement` | "implement", "fix this", "work on this", "build this", "add feature", any implementation request |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Twinsen81:
nit would it make sense to have two skills? One for diagnose and one for implement OR does the "plan" cover this? I was thinking of the situation where you want to do analysis before having AI jump into implement.

- **NEVER create a PR without explicit permission**
- When asked to "fix" or "update" something, that does NOT imply permission to commit/push
- Always wait for explicit "commit", "push", or "create PR" commands

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Twinsen81
What if we added something for branches/rebases "Do not create branches, rebase, or modify git history unless explicitly asked." ?

### 3c: Unit Tests

```bash
./gradlew aztec:testRelease
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing a ":" in front of aztec


**Test rules:**
- NEVER weaken or remove assertions to make tests pass
- NEVER modify production code just to pass a test without permission
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Twinsen81
Can we combine with something like this: "Don’t make unrelated/incorrect changes to production code solely to appease a test. If test reveals a real issue, fix it."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants