chore: weekly profile refresh - #55
Conversation
Refresh the three auto-managed blocks in profile/README.md: now-building and team-shipping from Linear (14d window), and recently-shipped from GitHub releases and merged PRs (7d window). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UowDc5VJV2qFKQbASFSYKR
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe guild profile now lists current roadmap work, recent releases, repository updates, and team priorities. ChangesGuild profile updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@profile/README.md`:
- Line 46: Update the “Community” bullet in the “Across the guild” section to
remove the guild-wide “Season Two” framing, while preserving the description of
the pilot gardens and PGSP first-cohort readiness. Use cohort wording without a
Season label unless an explicitly project-scoped official name is available.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: df75e052-7c82-4617-accd-6f59dc906b6f
📒 Files selected for processing (1)
profile/README.md
📜 Review details
🧰 Additional context used
📓 Path-based instructions (4)
profile/README.md
📄 CodeRabbit inference engine (CLAUDE.md)
Use absolute GitHub URLs in
profile/README.mdfor links back into this repo
Files:
profile/README.md
**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
Link to the issue-creation flow in docs that ask someone to "open" an issue or RFC, not just the source template file
**/*.md: Do not introduce guild-wide Season framing in documentation
Do not describe the dev guild as the entire Greenpill Network in documentation
Avoid growth-hacking and trend-chasing voice in documentation: no FOMO, virality, leaderboards, streaks, or AI-first framing
Files:
profile/README.md
**/*.{md,yml,yaml}
📄 CodeRabbit inference engine (CLAUDE.md)
Search for and retire stale terms:
app.charmverse.io,greenpill.network/dev-guild,FOMO,virality,leaderboards,streaks,AI-first, former dev-guild PM URL, retired funded-work file names, old GitHub grant lifecycle labels, and retired Claude routine filenamesDo not reintroduce the former dev-guild PM URL or old migration language for project-management state
Files:
profile/README.md
{CONTRIBUTING.md,GOVERNANCE.md,SECURITY.md,SUPPORT.md,profile/README.md,.github/ISSUE_TEMPLATE/**,.github/PULL_REQUEST_TEMPLATE.md}
📄 CodeRabbit inference engine (AGENTS.md)
Treat contact emails, disclosure SLAs, payout timing, and governance claims as sensitive public commitments and do not change them casually
Files:
profile/README.md
🔇 Additional comments (3)
profile/README.md (3)
25-29: LGTM!
35-36: LGTM!
44-45: LGTM!Also applies to: 47-48
| - **Marketing** — producing the Green Goods PWA onboarding how-to videos and the docs demo-video batch. | ||
| - **Product** — cutting the August v1.3.0 release after shipping the v1.2.1 patch and the indexer migration, having just locked the Commitment Pooling implementation architecture. | ||
| - **Research** — lining up methodology reviewers for the Impact Framework v0.1 refresh, and shaping the community engagement model behind Needs & Signals. | ||
| - **Community** — onboarding the Season Two pilot gardens, most recently an agroforestry pilot, with PGSP first-cohort readiness next in line. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Avoid guild-wide Season framing in this profile.
Because this wording appears in the guild profile’s “Across the guild” section, describe the cohort without the Season label unless Season Two is an official, project-scoped name.
Suggested wording
-- **Community** — onboarding the Season Two pilot gardens, most recently an agroforestry pilot, with PGSP first-cohort readiness next in line.
+- **Community** — onboarding the second pilot-garden cohort, most recently an agroforestry pilot, with PGSP first-cohort readiness next in line.As per coding guidelines, **/*.md must not introduce guild-wide Season framing in documentation.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - **Community** — onboarding the Season Two pilot gardens, most recently an agroforestry pilot, with PGSP first-cohort readiness next in line. | |
| - **Community** — onboarding the second pilot-garden cohort, most recently an agroforestry pilot, with PGSP first-cohort readiness next in line. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@profile/README.md` at line 46, Update the “Community” bullet in the “Across
the guild” section to remove the guild-wide “Season Two” framing, while
preserving the description of the pilot gardens and PGSP first-cohort readiness.
Use cohort wording without a Season label unless an explicitly project-scoped
official name is available.
Source: Coding guidelines
2 participants
Summary
Weekly
profile-refreshrun for 2026-W32. Refreshes the three auto-managed marker blocks inprofile/README.mdso the public org page reflects current work. Nothing outside the markers changed.Why
Scheduled guild routine (
routines/claude/profile-refresh.md). Keeps the public org page current without a human having to re-derive it each week.Closes # n/a
What changed
Sources and time windows
<!-- now-building --><!-- recently-shipped -->network-websitehad no release and no merged PR in the window, so it is skipped rather than given a placeholder.<!-- team-shipping -->Test plan
HEAD(scripted comparison, not eyeballed).git diff --stat= 1 file, 11 insertions / 11 deletions,profile/README.mdonly.profile/README.md— clean.Risk and rollout
Checklist
.env*files committedNotes for reviewer
CLAUDE.mdfails onroutines/claude/guild-grant-scout.md— but it's a false positive, matching a literal[text](url)used as markdown-syntax prose rather than a real link. Pre-existing onmain, untouched here; worth a checker tweak in a separate PR if it keeps tripping runs.greenpill-dev-guild/networkfeat: Convert issue templates to YAML forms + add PR template #15, Add 'How the Dev Guild Pays for Scoped Work' playbook (draft) #18) fell outside this routine's authorized repo scope and are minor agent-config housekeeping, so they are not represented in Recently shipped.🤖 Generated with Claude Code
https://claude.ai/code/session_01UowDc5VJV2qFKQbASFSYKR
Generated by Claude Code