molecule-ai/molecule-ai-org-template-molecule-dev
35
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
d758d3bf6e
molecule-ai-org-template-mo.../seo-growth-analyst/schedules/landingpage-seo-check.md
documentation-specialist d758d3bf6e
Some checks failed
CI / validate (push) Failing after 0s
Details
CI / validate (pull_request) Failing after 0s
Details
fix(install): sweep persona git-clone URLs to Gitea (#37) 
Sweeps 51 persona initial-prompt.md files + org.yaml + 2 schedule
files (55 substitutions across 50 files) plus a SHARED_RULES.md
DOCUMENTATION_POLICY link migration.

Per orchestrator's #37 A/B/C decision (Q1):
- PUBLIC repos (docs, molecule-sdk-python) → anonymous clone:
    https://git.moleculesai.app/molecule-ai/<repo>.git
- PRIVATE repos (internal, molecule-controlplane, molecule-core,
    molecule-app, landingpage, etc.) → GITEA_TOKEN-authed clone:
    https://oauth2:${GITEA_TOKEN}@git.moleculesai.app/molecule-ai/<repo>.git

Private-repo clones DEPEND ON the workspace-bootstrap pipeline
injecting GITEA_TOKEN — tracked at internal#44 (parked follow-up).
Until that lands, persona boot steps that clone private repos WILL
FAIL with a no-such-env-var error.

LEFT UNTOUCHED in this PR:
- gh CLI calls (gh repo clone, gh pr list, gh issue create, gh run
  list) — gh doesn't talk to Gitea. Migration to tea/curl/shim is
  tracked at internal#45 (parked follow-up).
- Narrative `Molecule-AI/<repo>` mentions (e.g. "PR against
  Molecule-AI/molecule-core") — these are typically gh-CLI flag args;
  separate concern, see #45.
- Historical issue/PR cross-refs (per Q3, leave-as-is for audit
  trail).

SHARED_RULES.md adds a "Post-2026-05-06 migration in progress"
callout at the top, naming both #44 (private-repo blocker) and #45
(gh CLI blocker), so persona authors hitting boot failures know what
to look up.

Refs: molecule-ai/internal#37, molecule-ai/internal#38,
molecule-ai/internal#42, molecule-ai/internal#44, molecule-ai/internal#45
2026-05-07 00:08:53 -07:00

882 B
Raw Blame History

Landing page SEO audit. You co-own Molecule-AI/landingpage with Content Marketer.

Step 1: Check repo

gh pr list --repo Molecule-AI/landingpage --state open --json number,title
gh issue list --repo Molecule-AI/landingpage --state open --json number,title

Step 2: SEO checks

  • Review any open PRs that touch SEO-related files (meta tags, structured data, sitemap)
  • Check if og:image, og:title, og:description are set correctly for each page
  • Verify sitemap is generating correctly
  • Check for i18n hreflang tags (en + zh)

Step 3: Act

Clone and fix if needed:

git clone https://oauth2:${GITEA_TOKEN}@git.moleculesai.app/molecule-ai/landingpage.git /workspace/repos/landingpage 2>/dev/null || (cd /workspace/repos/landingpage && git pull)

Step 4: Report

commit_memory "landingpage-seo HH:MM — PRs: N, issues: N, SEO status: "