chore: weekly profile refresh#49
Conversation
Refresh the recently-shipped and team-shipping marker blocks in profile/README.md. Now-building left byte-identical (still accurate). Sources: Linear (five teams, ~last 14 days) and GitHub (releases + merged PRs, 2026-07-13 to 2026-07-20).
|
Warning Review limit reached
Next review available in: 56 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. 📝 WalkthroughWalkthroughUpdated ChangesProfile README content
Estimated code review effort: 1 (Trivial) | ~3 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 description in the guild profile to replace the
season-based “Season Two” wording with neutral language such as “the second
pilot cohort,” unless it is confirmed to be an externally defined proper name.
🪄 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
Run ID: 27214d79-695a-4ada-96f8-9e005e2d8ec9
📒 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 (1)
profile/README.md (1)
35-37: LGTM!
Per AGENTS.md and README.md contributor guidance ("No guild-wide Season
framing"), reword the team-shipping Community bullet from "Season Two
pilot cohort" to neutral "next cohort of pilot gardens". Still scoped to
the team-shipping marker block only.
1 participant
Weekly
profile-refreshrun for 2026-W30. Only the two auto-managed marker blocks changed; the diff against the base commit touches nothing else (now-buildingand every other line are byte-identical). PR only — this branch never pushesmain; a human merges.Recently shipped — GitHub releases + merged PRs, 2026-07-13 → 2026-07-20
green-goodsmainthis week (its 10 in-window PRs all landed ondeveloptoward v1.3.0, which is "now building", not shipped).What each team is shipping — Linear, five teams, ~last 14 days
Refreshed each team line with current focus + a recent completion, all grounded in live Linear state: Product (v1.3.0 after shipping v1.2.0; commitment pooling), Research (GIF v0.1 refresh; taxonomy reconcile), Community (Season Two cohort; first PGSP cohort kicked off at Builder Space #23), Growth (Octant Epoch 12 active; Artizen Season 7 raise; grant queue), Marketing (PWA onboarding how-to videos + docs demo-video batch).
Now building — Linear active initiatives/projects
Left byte-identical: all five threads (Green Goods v1.3.0, PGSP, Network website, Commitment Pooling, Community Needs & Signals) are still In Progress / actively moving, so no change was warranted.
Guardrails
recently-shippedandteam-shippingmarker blocks — verified withgit diffagainst the base commit.🤖 Generated with Claude Code
https://claude.ai/code/session_01Bp4r6ytjoHUXeEar4ZXXtj
Generated by Claude Code