The .agents/workflows/ directory contains process guides for common development tasks. These workflows help AI assistants (and humans) follow consistent, high-quality practices.
| Workflow | When to Use |
|---|---|
| git-workflow.md | Branching strategies, commit conventions, collaboration |
| release-process.md | Version bumps, tagging, GitHub releases |
| Workflow | When to Use |
|---|---|
| feature-development.md | Building new features from start to merge |
| bug-fixing.md | Fixing bugs, including hotfix procedures |
| Workflow | When to Use |
|---|---|
| pr.md | Unified PR workflow (orchestrates all checks) |
| code-audit-remote.md | Remote auditing (CodeRabbit, Codacy, SonarCloud) |
| error-checking-feedback-loops.md | Monitoring CI/CD, fixing failures |
| Workflow | When to Use |
|---|---|
| multi-repo-workspace.md | Working across multiple repositories safely |
| Workflow | When to Use |
|---|---|
| wiki-update.md | Updating GitHub wiki from codebase changes |
| Workflow | When to Use |
|---|---|
| wordpress-local-testing.md | WordPress Playground, LocalWP, wp-env |
1. Check git-workflow.md for branching strategy
2. Use feature-development.md OR bug-fixing.md
3. Follow code-review.md before PR
1. Follow release-process.md step-by-step
2. Use error-checking-feedback-loops.md for CI monitoring
3. Create GitHub release with changelog
1. Read multi-repo-workspace.md FIRST
2. Always verify which repo you're in
3. Don't assume features from one repo exist in another
1. Build codebase context with Augment/Repomix
2. Review .wiki/ pages against current codebase
3. Update pages, commit to .wiki/ directory
4. Push to main - auto-syncs to GitHub wiki
When you say "Add a new feature for user authentication":
- AI reads
feature-development.md - Creates safe linked worktree following naming convention
- Implements feature with proper structure
- Follows code review checklist
- Prepares PR with appropriate description
When you say "Fix the login timeout issue":
- AI reads
bug-fixing.md - Determines if regular fix or hotfix needed
- Creates appropriate branch
- Fixes bug with proper testing
- Documents the fix in commit message
When you say "Release version 2.1.0":
- AI reads
release-process.md - Updates version in relevant files
- Updates CHANGELOG.md
- Creates annotated tag
- Pushes and creates GitHub release
These workflows work for:
- This aidevops repository
- Any other codebase
- WordPress projects
- General software development
Each workflow includes:
- Clear step-by-step instructions
- Code examples and commands
- Checklists for verification
- Troubleshooting sections
Following consistent workflows:
- Reduces errors
- Improves collaboration
- Creates audit trails
- Enables automation
# Get all quality feedback for current PR
bash ~/git/aidevops/.agents/scripts/quality-feedback-helper.sh status --pr NUMBER# Run local quality checks (fast, offline)
bash ~/git/aidevops/.agents/scripts/linters-local.sh# Watch for check completion
bash ~/git/aidevops/.agents/scripts/quality-feedback-helper.sh watch --pr NUMBER- The .agents Directory - Directory structure
- Understanding AGENTS.md - AI instruction file
- Getting Started - Installation and setup