d079af7cf9
PRs are for external contributors. Crew workers commit directly to main. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
63 lines
2.1 KiB
Markdown
63 lines
2.1 KiB
Markdown
# Agent Instructions
|
|
|
|
See [CLAUDE.md](CLAUDE.md) for full instructions.
|
|
|
|
This file exists for compatibility with tools that look for AGENTS.md.
|
|
|
|
## Key Sections in CLAUDE.md
|
|
|
|
- **Issue Tracking** - How to use bd for work management
|
|
- **Development Guidelines** - Code standards and testing
|
|
- **Visual Design System** - Status icons, colors, and semantic styling for CLI output
|
|
|
|
## Visual Design Anti-Patterns
|
|
|
|
**NEVER use emoji-style icons** (🔴🟠🟡🔵⚪) in CLI output. They cause cognitive overload.
|
|
|
|
**ALWAYS use small Unicode symbols** with semantic colors:
|
|
- Status: `○ ◐ ● ✓ ❄`
|
|
- Priority: `● P0` (filled circle with color)
|
|
|
|
See CLAUDE.md "Visual Design System" section for full guidance.
|
|
|
|
## Landing the Plane (Session Completion)
|
|
|
|
**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.
|
|
|
|
**MANDATORY WORKFLOW:**
|
|
|
|
1. **File issues for remaining work** - Create issues for anything that needs follow-up
|
|
2. **Run quality gates** (if code changed) - Tests, linters, builds
|
|
3. **Update issue status** - Close finished work, update in-progress items
|
|
4. **PUSH TO REMOTE** - This is MANDATORY:
|
|
```bash
|
|
git pull --rebase
|
|
bd sync
|
|
git push
|
|
git status # MUST show "up to date with origin"
|
|
```
|
|
5. **Clean up** - Clear stashes, prune remote branches
|
|
6. **Verify** - All changes committed AND pushed
|
|
7. **Hand off** - Provide context for next session
|
|
|
|
**CRITICAL RULES:**
|
|
- Work is NOT complete until `git push` succeeds
|
|
- NEVER stop before pushing - that leaves work stranded locally
|
|
- NEVER say "ready to push when you are" - YOU must push
|
|
- If push fails, resolve and retry until it succeeds
|
|
|
|
## ABSOLUTELY FORBIDDEN: Pull Requests
|
|
|
|
**NEVER create pull requests.** PRs are for external contributors, not for us.
|
|
|
|
We are the sole maintainer. Crew workers have direct commit access. The correct workflow is:
|
|
|
|
1. Make changes
|
|
2. Run tests
|
|
3. Commit directly to main
|
|
4. Push
|
|
|
|
If you find yourself typing `gh pr create` - STOP. You are doing it wrong. Just commit and push.
|
|
|
|
The PR Sheriff role reviews *incoming* PRs from *contributors*. We do not create PRs ourselves.
|