osc
/osc
Buduje tablicę problemów z repozytorium GitHub, czyli błędów, testów, lintu i porzuconych pull requestów, i rozwiązuje wybrany punkt w sprawdzonym PR.
- Autor
- kansalakshat ↗
- Repozytorium
- osc ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 6
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Buduje tablicę problemów z repozytorium GitHub, czyli błędów, testów, lintu i porzuconych pull requestów, i rozwiązuje wybrany punkt w sprawdzonym PR.
Wyzwalacze z opisu
Oryginalny opis (EN)
Give it a GitHub repo URL and it builds a Problem Board of every workable problem (issues, failing tests, lint errors, broken docs, fuzz bugs, abandoned PRs) with root cause, fix, test plan and size; then 'solve N' takes an item to a verified PR, paused for confirmation. Tuned for GSoC, LFX, MLH, Summer of Bitcoin, ESoC, C4GT. Use when the user gives a repo link and wants to contribute or prep for a mentorship program.
Jak działa
- Commands: read only the file the command needs
- Board file = memory
- Hard rules (all commands)
- Step 11: application kit (proposal)
Podgląd SKILL.md
---
name: osc
description: "Give it a GitHub repo URL and it builds a Problem Board of every workable problem (issues, failing tests, lint errors, broken docs, fuzz bugs, abandoned PRs) with root cause, fix, test plan and size; then 'solve N' takes an item to a verified PR, paused for confirmation. Tuned for GSoC, LFX, MLH, Summer of Bitcoin, ESoC, C4GT. Use when the user gives a repo link and wants to contribute or prep for a mentorship program."
triggers:
- "\\bosc\\b"
- "oss.?contribute"
- "contribute.?to"
- "find.?(me.?)?(an.?)?issues?"
- "open.?source.?contribution"
- "draft.?(a.?)?pr"
- "problem.?board"
- "solve.?#?\\d+"
- "gsoc|lfx|mlh.?fellowship|summer.?of.?bitcoin|esoc|c4gt|dmp"
---
# osc
Repo URL in, numbered Problem Board out. Per picked item: a verified PR on the
user's fork, paused for confirmation.
## Commands: read only the file the command needs
Files sit next to this one (`~/.claude/skills/osc/`). Don't read a file the
current command doesn't name. Already read this session? Don't re-read.
| User says | Read | Do |
|---|---|---|
| `<repo url>` | `board.md` | Steps 0-2: recon, scan, show board |
| `solve N` (any order) | `solve.md` | Steps 3-9 for item N |
| `verify N` / `more` | `board.md` "Deep triage" only | Triage item N / next ~10 unverified, update rows |
| `status` | none | Board table; refresh each `PR open` row with `gh pr view <PR> --json state,reviewDecision` |
| `reviews N` | `reviews.md` | Step 10 |
| `proposal` | none | Step 11 below |
## Board file = memory
`~/oss-boards/OWNER__REPO.md`. Always read it before acting on a number; never
trust a number from chat. Read only what you need, not the whole file:
```bash
B=~/oss-boards/OWNER__REPO.md
sed -n '1,/^## 1\./p' "$B" | head -n -1 # header + table
sed -n "/^## $N\./,/^## /p" "$B" | head -n -1 # item N section
```
## Hard rules (all commands)
- Nothing is pushed, opened, claimed, or commented without the user saying so.
Exceptions: fixes pushed to an already open PR (Step 10), and
`@coderabbitai review` when the bot didn't run (Step 9).
- **Messages to people** (GitHub, Discord, Slack, email, list): put the
ready-to-send draft in chat; never send it yourself. Follow the project's
format. Write like a busy developer: short, plain, no "This PR aims to",
"comprehensive", "robust", "seamless", "leverage", "ensure", no emoji.
- **Disclosure: the user always handles AI disclosure manually.** Never tick an
AI checkbox, pick an option, or write a disclosure statement, even if marked
mandatory. Leave it as the template has it, surface the exact policy wording,
remind the user before the PR opens. No policy: say nothing. Never add AI
co-author trailers; the user is sole author. Maintainers close unverified AI
work on sight ("Closing this as ai slop"); verification (Steps 4, 6) and the
user being able to explain it (Step 8) are what prevent that.
- **Pacing:** max 2 open PRs per repo. Merged beats opened; three small merged
fixes in one org beat thirty drive-bys.
- **Keep tool output small.** Long-running output (tests, lint, builds, fuzz)
goes to a log file; read `tail -40` or `grep` it, never dump it. Use `--json`
+ `--jq` on `gh` calls; never `--comments` or raw bodies of bot walkthroughs.
- **GitHub rate limits:** use `gh issue list`/`gh pr list` (GraphQL), not
`gh api search/issues --paginate`. On a 403 rate limit, `gh api rate_limit`
and wait for the reset; never retry in a loop.
## Step 11: application kit (`proposal`)
From the board's `merged` and `PR open` rows:
- Contributions list: PR link, one-line user-facing impact, status.
- Areas of the codebase touched, mapped to the program idea being applied for.
- A draft paragraph in the user's voice, which they rewrite. Programs screen
for people who understand their own work.
Pliki w paczce (6)
- LICENSE 1 KB
- README.md 2 KB
- SKILL.md 4 KB
- board.md 9 KB
- reviews.md 2 KB
- solve.md 5 KB
Wersje
W bazie nie ma innych skilli o nazwie osc.
Migawka bazy z 13.11.2026 · wersja paczki d203dfdc531d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100contributor
Prowadzi cały proces wkładu w open source: wyszukiwanie zgłoszeń, fork repozytorium, poprawkę błędu i wysłanie pull requesta. - 100copilot-code-reviewer
Stosuje metodę recenzji seniora do pull requestów w repozytorium lfx-skills, niezależnie od tego, co zmieniają. - 100media-osc
Opisuje protokół Open Sound Control (OSC 1.0 i 1.1): układ pakietów, bundle z timetagami, dopasowanie wzorców adresów, UDP, TCP i SLIP, liblo oraz python-osc, mosty do MIDI i DMX. - 100solve-issue
Rozwiązuje zgłoszenie GitHub od początku do końca i otwiera pull request z poprawką, po podaniu numeru lub linku. - 100lfx
Kieruje zadaniami obejmującymi wiele repozytoriów LFX: wskazuje, które repozytorium czym zarządza, co dotyka zmiana, kto czego używa, i podaje ścieżki plików w repozytoriach partnerskich. - 90github
Przeszukuje i czyta pull requesty, issues i kod w skonfigurowanej organizacji lub repozytorium, na potrzeby przeglądów.