chore: publish the pm-workflow skill at project scope - #23
Conversation
Vendors the PM-orchestrated planner/programmer/qa workflow skill into the repo so collaborators get it on clone. Canonical copy lives in .agents/; .claude/skills/pm-workflow is a repo-relative symlink to it. Excluded from Prettier since the skill is replaced wholesale by its own updater and reformatting would churn against every upgrade.
|
Warning Review limit reached
Next review available in: 8 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. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (20)
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 |
1 participant
Summary
Vendors the PM-orchestrated planner/programmer/qa workflow skill (v2.1.1) into the repo at project scope, so collaborators get it on clone.
.agents/skills/pm-workflow/(tool-agnostic).claude/skills/pm-workflowis a repo-relative symlink (mode120000, target../../.agents/skills/pm-workflow), so it resolves for anyone who clonesScoping — what is deliberately NOT published
This repo runs the workflow in
privatevisibility mode, so everything else workflow-related stays local. Verified viagit add -An .dry-run that the only exposed paths are the skill itself:.claude/projects/— session memory and a user profile — excluded.claude/agents/,settings.local.json,scheduled_tasks.lock— excludeddocs/, rootAGENTS.md/CLAUDE.md— excludedScanned all 17 skill files for credentials, absolute/local paths, personal identifiers, and project-specific references: clean.
Two exclusion bugs fixed along the way
AGENTS.md/CLAUDE.mdpatterns in.git/info/excludewere unanchored, so they also swallowed the skill's owntemplates/AGENTS.mdandtemplates/CLAUDE.md. Only 14 of 17 files would have been published — a broken skill. Root-anchored those rules (/AGENTS.md), which was their intent anyway.settings.local.jsonwas caught by.gitignore; added a narrow negation for the skill's template copy only. Verified it holds no machine-local state ({"fallbackModel": ["sonnet"]}).Lint
The skill is vendored and replaced wholesale by its own updater, so reformatting it would churn against every upgrade — added to
.prettierignore, same precedent asgraphify-out/.prettier --check .— exit 0eslint . --max-warnings 68— exit 0, still exactly 68 warnings (unchanged baseline)120000with a repo-relative target