15ac834239
- org.yaml: Remove required_env (PR #1031), update category_routing for new roles - New workspace roles (9): backend-engineer-3, frontend-engineer-2/3, fullstack-engineer, platform-engineer, qa-engineer-2/3, security-auditor-2, triage-operator-2 - Wire existing backend-engineer-2 and sre-engineer into teams/dev.yaml hierarchy - Triage operators: add MERGE AUTHORITY as #1 priority, multi-repo coverage - Security auditor: multi-repo rotation across all org repos - QA: dedicated coverage for controlplane+proxy and app+docs - Marketing schedules: add TTS, music, lyrics, image, video capabilities - Research sub-agents: add */30 research/competitor/market cycles with web_search - All schedules: add "IMPORTANT: Check internal repo" directive - Leader pulses: expanded team scan to include all new roles - Dev-lead: updated dispatch mapping for 16 engineering roles Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.5 KiB
IMPORTANT: Check Molecule-AI/internal repo for roadmap (PLAN.md), known issues, runbooks before starting work.
Recurring code quality audit. Be thorough and incremental. NOTE: QA Engineer 2 covers molecule-controlplane + molecule-tenant-proxy. QA Engineer 3 covers molecule-app + docs. You own molecule-core as primary scope. Coordinate to avoid duplicate coverage across the org.
- Pull latest: cd /workspace/repo && git pull
- Check what you audited last time: use search_memory("qa audit") to recall prior findings
- See what changed since last audit: git log --oneline --since="12 hours ago"
- Run ALL test suites and record results: cd /workspace/repo/platform && go test -race ./... 2>&1 | tail -20 cd /workspace/repo/canvas && npm test 2>&1 | tail -10 cd /workspace/repo/workspace-template && python -m pytest --tb=short -q 2>&1 | tail -10
- Check test coverage on recently changed files:
- For each changed Python file, check if it has corresponding tests
- For each changed Go handler, check if it has test coverage
- For each changed .tsx component, check if it has a .test.tsx
- Review recent PRs for quality issues: cd /workspace/repo && gh pr list --state merged --limit 5 For each: check if tests were added, if docs were updated, if 'use client' is present on hook-using .tsx
- Check for regressions: cd /workspace/repo/canvas && npm run build 2>&1 | tail -5 Look for TypeScript errors, missing exports, build warnings
- Record your findings to memory:
Use commit_memory with key "qa-audit-latest" and value containing:
- Date and commit hash audited up to
- Test counts (Go, Python, Canvas) and pass/fail status
- Files with missing test coverage
- Quality issues found
- Areas to investigate deeper next time === FINAL STEP — DELIVERABLE ROUTING (MANDATORY every cycle) ===
a. For each failing test, build break, or coverage regression: FILE A GITHUB ISSUE:
- Dedupe: gh issue list --repo Molecule-AI/molecule-monorepo --search "" --state open
- If new: gh issue create --title "qa: — " --body with failure log, commit SHA, reproducer command, suspected file:line, proposed approach
- Capture issue numbers for the PM summary.
b. delegate_task to PM with a summary: audit SHA, test counts (Go/Python/Canvas), pass/fail, new issue numbers, top 3 risks. PM routes to dev.
c. If all clean: delegate_task to PM with "qa clean on SHA " so the audit is observable.
d. Save to memory key 'qa-audit-latest' as a secondary record only.