pave-contribute
Contribute a session learning back to the upstream tonone repo. Scans the conversation, extracts the single most reusable insight, asks one question, creates the PR. Use when asked to "contribute a learning", "share a discovery", "improve tonone", or "submit a fix upstream".
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill pave-contribute --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Contribute to tonone You are Pave. Scan the session. Find the learning. One question. PR. Done. --- ## Step 1 — Extract the learning (no user input needed) Read the current conversation and find the single most reusable insight. Look for: - A **routing gap**: user's request didn't match any skill, they worked around it - **Agent corrections**: user corrected the same agent 2+ times for the same pattern - A **missing skill**: user built something that should exist as a `/skill-name` - A **prompt improvement**: agent's default behavior needed explicit correction Score candidates by reusability (would this help ANY tonone user, not just this project?). Pick the highest-scoring one. If nothing qualifies, print: ``` ╭─ PAVE ── contribute ─────────────────────────────╮ No reusable learnings found in this session. ╰──────────────────────────────────────────────────╯ ``` ...and exit. --- ## Step 2 — Map to a file change Determine exactly what to change in the tonone repo: | Learning type | File to change | | ------------------ | ---------------------------------------------- | | routing gap | `CLAUDE.md` — add routing rule | | agent correction | `agents/<name>.md` — patch system prompt |
- Step 1 — Extract the learning (no user input needed)
- Step 2 — Map to a file change
- Step 3 — Sanitize (automatic, no asking)
- Step 4 — One question
- Step 5 — Create the PR (no further questions)
- Step 6 — Receipt
- Error handling
git clone https://github.com/tonone-ai/tonone "$TONONE_TMP/tonone" --depth=1 --quiet
cd "$TONONE_TMP/tonone"
gh repo fork --remote-name=fork --clone=false 2>/dev/null || true
git remote add fork "https://github.com/${GH_USER}/tonone.git" 2>/dev/null || \
git remote set-url fork "https://github.com/${GH_USER}/tonone.git"
git checkout -b "$BRANCH"
git add -A
git commit -m "contribute: <one-line description>"
git push fork "$BRANCH" --quiet
rm -rf "$TONONE_TMP"What does the pave-contribute skill do?
Contribute a session learning back to the upstream tonone repo. Scans the conversation, extracts the single most reusable insight, asks one question, creates the PR. Use when asked to "contribute a learning", "share a discovery", "improve tonone", or "submit a fix upstream".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill pave-contribute --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.