scout
/scout
Ocenia przed kodowaniem, czy warto zgłaszać PR-y do repozytorium na GitHubie: czy obcy mogą wnosić zmiany i czy zadania są zajęte. Przydaje się przy wyborze projektu.
- Autor
- ahmad-punch ↗
- Repozytorium
- oss-contributor ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 11.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 11.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
Ocenia przed kodowaniem, czy warto zgłaszać PR-y do repozytorium na GitHubie: czy obcy mogą wnosić zmiany i czy zadania są zajęte. Przydaje się przy wyborze projektu.
Argumenty
/scout <owner/repo or GitHub URL>
Oryginalny opis (EN)
Give a go or no-go on contributing to a GitHub repository before any code is written. Checks whether outsiders can open PRs at all, how often outside PRs get merged, whether good-first-issues are stale or claimed, and what the AI and contribution policy files say. Use when choosing a project or an issue to work on.
Jak działa
- Step 1: Can outsiders open PRs?
- Step 2: Outsider merge rate
- Step 3: Good first issues
- Step 4: Policy files
- Step 5: Verdict
Podgląd SKILL.md
---
name: scout
description: Give a go or no-go on contributing to a GitHub repository before any code is written. Checks whether outsiders can open PRs at all, how often outside PRs get merged, whether good-first-issues are stale or claimed, and what the AI and contribution policy files say. Use when choosing a project or an issue to work on.
argument-hint: "<owner/repo or GitHub URL>"
user-invocable: false
allowed-tools: Read Grep Glob Bash(gh api *) Bash(gh repo view *) Bash(gh issue list *) Bash(gh pr list *) Bash(date *)
---
# Scout
Decide whether `$ARGUMENTS` (`owner/repo` or a GitHub URL; if empty, use the current repo from `gh repo view --json nameWithOwner`) is worth contributing to right now. Everything here is read-only.
If the `contrib-scout` plugin or CLI is installed (a `/contrib-scout` command is available, or `command -v contrib-scout` succeeds), prefer it: run it on the repo and use its output for steps 1 to 3, then continue at step 4. Otherwise do the checks below with `gh`.
## Step 1: Can outsiders open PRs?
```bash
gh api repos/{owner}/{repo} --jq '{archived, disabled, fork, default_branch, pushed_at, open_issues_count, pull_request_creation_policy, has_issues}'
```
- `archived: true`, or `pull_request_creation_policy` set to anything other than `all` (for example collaborators only): **no-go**. Say so and stop.
- `pushed_at` older than six months: flag the project as possibly inactive.
- If the field is missing from the response (older API or GHES), say it could not be checked and continue.
## Step 2: Outsider merge rate
Count closed PRs from the last six months, keep the ones from outside contributors (opened from a fork and not by an owner, member or collaborator), and see how many were merged. Replace `SINCE` with the date six months ago (`date -v-6m +%F` on macOS, `date -d '6 months ago' +%F` on Linux):
```bash
gh api graphql \
-f q='repo:{owner}/{repo} is:pr is:closed created:>SINCE' \
-f query='query($q:String!){search(query:$q,type:ISSUE,first:100){issueCount nodes{... on PullRequest{merged isCrossRepository authorAssociation createdAt mergedAt closedAt}}}}' \
--jq '[.data.search.nodes[] | select(.isCrossRepository and (.authorAssociation | IN("OWNER","MEMBER","COLLABORATOR") | not))] | {outsider_closed: length, outsider_merged: (map(select(.merged)) | length)}'
```
Report the rate as `merged / closed` with the sample size. Fewer than 5 outsider PRs is too small to judge; say so. As a rough guide: below 20% is a warning sign, above 50% is healthy. Also check open outsider PRs with no response:
```bash
gh pr list --repo {owner}/{repo} --state open --limit 50 --json number,createdAt,authorAssociation,comments,reviews --jq '[.[] | select((.authorAssociation | IN("OWNER","MEMBER","COLLABORATOR") | not) and (.comments | length) == 0 and (.reviews | length) == 0)] | length'
```
## Step 3: Good first issues
```bash
gh issue list --repo {owner}/{repo} --state open --label "good first issue" --limit 30 --json number,title,createdAt,updatedAt,assignees,comments
```
Try `"good-first-issue"` and `"help wanted"` too if the first label returns nothing. For each issue note age, days since last update, whether it is assigned, and whether comments already claim it ("I'd like to work on this"). Issues untouched for more than 90 days, or with several claim comments and no maintainer reply, are stale. Say how many are actually available.
## Step 4: Policy files
Fetch the policy files without cloning:
```bash
gh api repos/{owner}/{repo}/contents/CONTRIBUTING.md --jq .content | base64 --decode
```
Repeat for `AI_POLICY.md`, `.github/CONTRIBUTING.md`, `.github/AI_POLICY.md`, `AGENTS.md`, `.github/PULL_REQUEST_TEMPLATE.md`, and `.github/CODEOWNERS`; a 404 means the file is absent. Read them and record:
- AI stance: banned, agents banned, disclosure required, encouraged, silent. Quote the sentence.
- Gates: CLA or DCO, assignment before work, issue required for every PR, restrictions on `good first issue` for AI users.
- Anything that rules out the author's planned approach.
If the stance is a ban and the author works with AI assistance, the answer is **no-go** regardless of the numbers.
## Step 5: Verdict
```
## Scout: <owner/repo>
Verdict: GO | CAUTION | NO-GO
PR creation policy: <value or "not reported">
Activity: last push <date>
Outsider merge rate (6 months): <merged>/<closed> (<pct>%)
Unanswered outsider PRs: <n> of <open>
Good first issues: <available> available, <stale> stale, <claimed> claimed
AI policy: <stance> (<file>: "<quote>")
Gates: <CLA/DCO, assignment, issue-first, other>
Best candidates: #<n> <title> (<why>)
Reasons: <two or three lines>
```
Give the verdict from the evidence, not from the project's popularity. If a check failed (rate limit, permissions), list it under Reasons instead of guessing.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · ahmad-punch/oss-contributor | 100 | MIT |
| anton-abyzov/vskill | 100 | MIT |
| mcorbett51090/ravenclaude | 100 | MIT |
| kovrichard/portable-agent-layer | 100 | MIT |
| vanducng/skills | 100 | MIT |
| udaysharmadev/Skills | 100 | MIT |
| dodobrands/scout | 100 | Apache-2.0 |
| vaayne/agent-kit | 100 | MIT |
| yandmed/skill-scout | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 844b065c05c1 (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
- 100scout-issue
Wyszukuje i ocenia w GitHubie zgłoszenia dla początkujących, dopasowane do poziomu i czasu dewelopera. - 100authoring-issues-prs
Pomaga zgłaszać błędy, tworzyć issues na GitHubie, epiki i pull requesty: kieruje zmianę do właściwego repozytorium, dobiera formularz, dzieli pracę na jeden PR i stosuje CONTRIBUTING.md. - 100find-issues
Znajduje otwarte zgłoszenia w jednym repozytorium GitHub, które pasują do profilu kontrybutora, np. good first issue. - 100contributor
Prowadzi cały proces wkładu w open source: wyszukiwanie zgłoszeń, fork repozytorium, poprawkę błędu i wysłanie pull requesta. - 100github-repo-scout
Bada repozytorium GitHub z adresu URL: przegląda README, drzewo plików i stan lokalnego klonu oraz podaje zalecane następne kroki. - 100review-prs
Przegląda na prośbę jeden lub więcej pull requestów na GitHubie, także te otwarte przez agentów, a nie lokalne zmiany.