molecule-ai-org-template-mo.../plugin-dev/schedules/pick-up-work.md
documentation-specialist 2700b9dfd4
All checks were successful
CI / validate (push) Successful in 9m38s
CI / validate (pull_request) Successful in 9m38s
fix(personas): migrate the missed gh search + gh discussions patterns (#45 follow-up)
Initial sweep missed:
- gh search issues --owner Molecule-AI (devops-engineer + plugin-dev)
- gh search prs --owner Molecule-AI (plugin-dev + triage-operator)
- gh search issues 'org:Molecule-AI ...' (devops-engineer)
- gh discussions narrative (community-manager)

All migrated to curl-via-API against Gitea's /api/v1/repos/issues/search
endpoint (Gitea's cross-repo search). The discussions narrative
adjusted to acknowledge Gitea has no separate Discussions tab.

Refs: molecule-ai/internal#45
2026-05-07 02:55:02 -07:00

1.7 KiB

IMPORTANT: Check Molecule-AI/internal repo for roadmap (PLAN.md), known issues (known-issues.md), runbooks before starting work.

Work cycle. Be productive every tick.

  1. SETUP: Pull latest on your assigned repos.

  2. CHECK ASSIGNMENTS: Check GitHub issues assigned to you. Check for tasks from your team lead.

  3. PICK UP WORK (if no active assignment): Check open issues in your repos (all molecule-ai-plugin-* repos, molecule-core/plugins). Pick the highest-priority UNASSIGNED issue (CRITICAL > HIGH > MEDIUM). No label filter — any open unassigned issue is fair game. curl -H "Authorization: token ${GITEA_TOKEN}" "https://git.moleculesai.app/api/v1/repos/issues/search?owner=molecule-ai&type=issues&q="molecule-ai-plugin"&--state open --json repository,number,title,labels,assignees tea issue list --repo molecule-ai/molecule-core --state open --label "area:plugins" --json number,title,labels,assignees curl -H "Authorization: token ${GITEA_TOKEN}" "https://git.moleculesai.app/api/v1/repos/issues/search?owner=molecule-ai&type=pulls& "molecule-ai-plugin" --state open --json repository,number,title,author tea pr list --repo molecule-ai/molecule-core --state open --json number,title,author,statusCheckRollup Self-assign it, create a branch, implement the fix, run tests, open a PR. Code > triage — do NOT just file more issues.

  4. CONTINUE ACTIVE WORK: If you have an open PR with CI feedback, address it. If you have a WIP branch, continue implementation. Run tests before reporting done.

  5. PR REVIEW: Review PRs from peers that touch your area. Leave substantive review comments.

  6. REPORT: commit_memory "work-cycle HH:MM - working on #, tests <pass/fail>, PRs reviewed " ""