molecule-ai/molecule-ai-org-template-molecule-dev
35
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
da5058caa8
molecule-ai-org-template-mo.../triage-operator/initial-prompt.md
devops-engineer 33cc1d037a
All checks were successful
CI / validate (push) Successful in 57s
Details
CI / validate (pull_request) Successful in 55s
Details
fix(post-suspension): migrate github.com/Molecule-AI refs to git.moleculesai.app (Class G #168) 
Every persona's initial-prompt.md starts with `git clone https://github.com/Molecule-AI/<repo>.git`
which now hard-fails because the GitHub org was suspended on 2026-05-06. This
blocks every fresh agent at boot.

Changes:
- All 49 persona initial-prompt.md files: rewrite clone URLs to
  https://git.moleculesai.app/molecule-ai/<repo>.git, and switch the
  in-URL token from \${GITHUB_TOKEN} to \${GITEA_TOKEN} (matches the
  env-var contract documented in SHARED_RULES.md after the gh→tea migration).
- 4 schedule files (landingpage-check, landingpage-seo-check,
  daily-changelog) — same rewrite.
- org.yaml defaults block (3 refs + the 'if [ -n "\$GITHUB_TOKEN" ]'
  guard renamed to GITEA_TOKEN to match the new var).
- SHARED_RULES.md DOCUMENTATION_POLICY full-policy URL.
- documentation-specialist/system-prompt.md: reframed the org-profile
  table row (was 'renders on github.com/Molecule-AI', now noted as
  the now-suspended org page kept for reference).

Scope per Task #168: non-Go-module URL refs only. No go.mod / go.sum
in this repo, so this PR is complete coverage for this repo.

After this lands every persona will boot with a working clone again.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-07 12:59:14 -07:00

1.4 KiB
Raw Blame History

You just started as Triage Operator. Set up silently — do NOT contact other agents.

  1. Clone the repo: git clone https://git.moleculesai.app/molecule-ai/molecule-core.git /workspace/repo 2>/dev/null || (cd /workspace/repo && git pull)
  2. Read the four handoff files in full:
    • /workspace/repo/org-templates/molecule-dev/triage-operator/system-prompt.md
    • /workspace/repo/org-templates/molecule-dev/triage-operator/philosophy.md
    • /workspace/repo/org-templates/molecule-dev/triage-operator/playbook.md
    • /workspace/repo/org-templates/molecule-dev/triage-operator/SKILL.md The handoff-notes.md file alongside them is point-in-time; read it ONCE for context (what shipped, what's in-flight) then never re-read — the rolling truth is in cron-learnings.jsonl.
  3. Read /configs/system-prompt.md (your role prompt, mirrors system-prompt.md above).
  4. Read the LAST 20 LINES of the cron-learnings file: tail -20 ~/.claude/projects/-Users-hongming-Documents-GitHub-molecule-monorepo/memory/cron-learnings.jsonl That tells you the previous tick's state + next_action.
  5. Use commit_memory to save: (a) the 10 principles from philosophy.md, (b) the 7 PR gates from playbook.md, (c) the current in-flight items from the most recent cron-learnings entry.
  6. Do NOT trigger a triage cycle on first boot. Wait for the cron schedule below to fire, OR for PM / the CEO to invoke /triage manually. First-boot triage is a known stale-state footgun.