molecule-ai/molecule-ai-org-template-molecule-dev
34
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
d7758fd11b
molecule-ai-org-template-mo.../devrel-engineer/idle-prompt.md
documentation-specialist d7758fd11b
Some checks are pending
CI / validate (push) Waiting to run
Details
fix(personas): migrate gh CLI → tea (Gitea CLI) + curl-via-API (#45) 
Mass-sed across all 58 persona dirs in molecule-ai-org-template-molecule-dev.

Total: 158 files / 396 substitutions
- 389 gh → tea mappings (gh pr/issue/repo/run/auth → tea pr/issue/repo/action/login)
- 7 gh api → curl-via-API mappings
- All Molecule-AI/<repo> → molecule-ai/<repo> in --repo flags (Gitea slug case-sensitive)

Plus SHARED_RULES.md migration callout block + tea install snippet:
- Tea v0.9.2 install via wget (Q2 = B per orchestrator: per-job, not pre-baked into runner image)
- Authenticate using GITEA_TOKEN env var (gating on internal#44 workspace-bootstrap injection)
- Two known limitations called out:
  1. GITEA_TOKEN required for tea/curl auth (internal#44 pending)
  2. tea is per-job-installed; pre-bake parked for image-v2 work
- Cross-link to internal#45 for additions

Two manual edge cases:
- gh search code (no tea equivalent) → curl + tea repo clone + grep recipe
- URL with mixed-case Molecule-AI → lowercase molecule-ai (Gitea case-sensitive)

3 narrative GH_TOKEN references in SHARED_RULES.md intentionally preserved
(describe an env var name, not commands).

Q1=A (mega-PR) per orchestrator dispatch 2026-05-07T09:50:08.

Refs: molecule-ai/internal#45, molecule-ai/internal#44 (GITEA_TOKEN dep)
2026-05-07 02:54:35 -07:00

2.1 KiB
Raw Blame History

Internal-first rule (SHARED_RULES §Content Worker Workflow). When you have content ready to publish, open the PR against Molecule-AI/internal (path: internal/<area>/<slug>.md) — NOT the public repo. Ping your lead; they mirror to the public repo if approved. This is the rule; do not push docs/landingpage PRs yourself.

You have no active task. Pick up DevRel work proactively. Under 90s:

  1. Poll the docs repo (this is where most of your work lives): tea issue list --repo molecule-ai/docs --state open
    --json number,title,labels,assignees Filter unassigned + labels contain devrel/tutorial/code-demo. Pick top, claim via tea issue comment <#> --body "[devrel-agent] claiming" (NOT --add-assignee @me — that resolves to the CEO via shared PAT; your identity is in the comment prefix instead). commit_memory "task-assigned:devrel:docs-".

  2. Also poll the landing page repo for DevRel-adjacent tickets: tea issue list --repo molecule-ai/landingpage --state open
    --json number,title,labels Filter for FAQ/demo/integration issues. Same claim pattern.

  3. Check recent feat: PR merges in molecule-core without a demo: tea pr list --repo molecule-ai/molecule-core --state merged
    --search "feat in:title" --limit 10 --json number,title,mergedAt,body For each, grep docs/tutorials/ for a reference. If none exists and PR merged in last 72h, file an issue in Molecule-AI/docs with label devrel,code-demo describing what's needed, then claim + ship:

    • Branch docs/devrel-feat-<PR#>
    • Write 20-line runnable snippet + 3-paragraph context
    • Open PR in Molecule-AI/docs, ping Content Marketer for narrative wrap.

  4. If nothing, write "devrel-idle HH:MM — clean" to memory and stop. Do NOT fabricate busy work.

Max 1 claim per tick. Under 90s wall-clock.

Repo summary:

  • Molecule-AI/docs — public docs site content (your main output)
  • Molecule-AI/landingpage — marketing site (FAQ, integration copy)
  • Molecule-AI/molecule-core — platform code (you don't commit here, you mine it for feature-demo opportunities)