Add workflow section: where to find tasks and review process
- Gitea issues location (tea CLI and web UI) - Priority order (CRITICAL > HIGH > MEDIUM/LOW) - Engineer workflow (pick up issue → branch → PR → wait for review) - Reviewer workflow (Yurii, Victoria, Arthur review PRs) - You merge approved PRs
This commit is contained in:
parent
d10c3f8e23
commit
fd27a9d173
|
|
@ -556,7 +556,34 @@ not just pattern matches. Grep catches the letter; LLM catches the intent.
|
|||
2. Run LLM analysis on all files changed since last review
|
||||
3. Address any findings before new feature work
|
||||
|
||||
### LLM Audit Prompt
|
||||
### Where to find your tasks
|
||||
|
||||
**Gitea Issues (https://git.clavitor.ai):**
|
||||
- Issues assigned to you: `tea issues list --repo johan/clavitor --assignees <your-name>`
|
||||
- Or: https://git.clavitor.ai/johan/clavitor/issues?q=assignee%3A<your-name>
|
||||
|
||||
**Priority order:**
|
||||
1. CRITICAL issues (fix immediately)
|
||||
2. HIGH priority issues (this sprint)
|
||||
3. MEDIUM/LOW (backlog)
|
||||
|
||||
### The review workflow
|
||||
|
||||
**Engineers (Sarah, Charles, Hans, etc.):**
|
||||
1. Pick up assigned issue
|
||||
2. Create branch: `git checkout -b <name>/fix-###`
|
||||
3. Implement fix per issue spec
|
||||
4. Create PR referencing issue: `Fixes ####` in commit
|
||||
5. **Wait for reviewer approval** — never merge your own PR
|
||||
|
||||
**Reviewers (Yurii, Victoria, Arthur):**
|
||||
- Review PRs for principle compliance
|
||||
- Comment: "Approved" or "Request changes"
|
||||
- Engineers address feedback, push updates
|
||||
|
||||
**You (Johan):**
|
||||
- Merge approved PRs
|
||||
- Override only in emergencies (document in PR)
|
||||
|
||||
Use this prompt with your LLM code review tool:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue