crbug
/crbug
Pobiera publiczne dane zgłoszenia Chromium, w tym opis i komentarze, i pomaga zrozumieć oraz rozwiązać problem.
- Autor
- chromium ↗
- Repozytorium
- chromium ↗
- Licencja
- BSD-3-Clause
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 2
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 4
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
BSD-3-Clause, otwarta.
- 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/fetch_crbug.py, scripts/fetch_crbug_test.py
Co robi i kiedy
Pobiera publiczne dane zgłoszenia Chromium, w tym opis i komentarze, i pomaga zrozumieć oraz rozwiązać problem.
Oryginalny opis (EN)
Triggers when the user mentions, asks to open/fetch, or requests action on (e.g., fix, investigate, resolve) a Chromium issue or bug report (e.g., crbug.com/123456, https://issues.chromium.org/issues/123456, bug 123456, or issue 123456). Fetches public issue metadata, description, and comments from issues.chromium.org (including resolving legacy Monorail IDs via crbug.com) and gracefully handles restricted or unreachable issues.
Jak działa
- Usage
- Step-by-Step Workflow
- Error & Failure Handling
Podgląd SKILL.md
--- name: crbug description: >- Triggers when the user mentions, asks to open/fetch, or requests action on (e.g., fix, investigate, resolve) a Chromium issue or bug report (e.g., crbug.com/123456, https://issues.chromium.org/issues/123456, bug 123456, or issue 123456). Fetches public issue metadata, description, and comments from issues.chromium.org (including resolving legacy Monorail IDs via crbug.com) and gracefully handles restricted or unreachable issues. --- # Chromium Issue (crbug) Fetcher When the user mentions, asks to open/fetch, or requests action on (e.g., fix, investigate, resolve) a Chromium bug or issue, follow this workflow to retrieve the issue context. > **Internal / Restricted Issues (HTTP 401/403):** If the user references a > Google-internal issue tracker URL or if `fetch_crbug.py` reports that the > issue requires authentication (restricted visibility), use the internal > `buganizer-ticket` skill if available in your workspace. ______________________________________________________________________ ## Usage Match any occurrences of: - `(?:https?://)?crbug\.com/(?:[a-zA-Z0-9_-]+/)?\d+` (e.g. `crbug.com/40256175`, `https://crbug.com/1422675`, `crbug.com/v8/12345`) - `https?://issues\.chromium\.org/(?:u/\d+/)?issues/\d+` (e.g. `https://issues.chromium.org/issues/40256175`) - `https?://bugs\.chromium\.org/p/[a-zA-Z0-9_-]+/issues/detail\?id=\d+` - `\bissues?[/\s]+\d+\b` (e.g. `issue 40256175`, `issues/40256175`) - `\bbug\s+\d+\b` (e.g. `bug 40256175`) ______________________________________________________________________ ## Step-by-Step Workflow ### Step 1: Extract Issue ID Extract the numeric issue ID or URL (e.g. `40256175` or `crbug.com/1422675`) from the user prompt. Both migrated IssueTracker IDs (`>= 10000000`) and legacy Monorail IDs (`< 10000000`) are supported. ______________________________________________________________________ ### Step 2: Run the Python Extraction Script Execute `fetch_crbug.py` from the Chromium `src` directory: - **Linux / macOS**: ```bash vpython3 agents/skills/crbug/scripts/fetch_crbug.py <ISSUE_ID_OR_URL> ``` - **Windows**: ```cmd vpython3 agents\skills\crbug\scripts\fetch_crbug.py <ISSUE_ID_OR_URL> ``` *(If skills are symlinked into `.agents/skills/`, you may also invoke `.agents/skills/crbug/scripts/fetch_crbug.py`).* By default, the bodies of `<details>` blocks (e.g. full commit details posted by the Git Watcher bot) are elided, keeping only their `<summary>`. If an elided block is relevant, rerun the script with `--expand-details`. > **Note (Sandbox & Network Requirements):** `fetch_crbug.py` makes outbound > HTTPS requests to `crbug.com` and `issues.chromium.org`. If your agent > environment blocks network access inside a sandbox, run the script outside the > sandbox. ______________________________________________________________________ ### Step 3: Format and Present Issue Details Format the extracted issue data into clean, structured Markdown: 1. **Header & Metadata**: - Issue ID with clickable link (`https://crbug.com/<ID>`) - Title - Component ID - Status - Type, Priority, Severity - Reporter and Assignee 2. **Description**: The original issue description and reproduction steps. 3. **Recent Comments**: Key updates or discussions from the comment thread. ______________________________________________________________________ ## Error & Failure Handling ### Restricted Issues (HTTP 401 / 403) If `fetch_crbug.py` fails because the issue has restricted access (e.g., histogram-expiry bugs, security bugs, or internal tickets): 1. Check if the internal `buganizer-ticket` skill is available in your environment and use it to fetch the issue with authenticated credentials. 2. Otherwise, follow the **Retrieval Failure Guardrails** below. ### Retrieval Failure Guardrails If `fetch_crbug.py` (and `buganizer-ticket`, if available) fails to retrieve the issue: 1. **Do not hallucinate or guess** the contents of the issue. 2. **Do not run raw shell commands** (`curl`, `wget`, etc.) against `crbug.com`, `issues.chromium.org`, or `issuetracker.google.com`. 3. **Prompt the user directly** to provide the issue details manually: > "Unable to retrieve Chromium issue `<ISSUE_ID>` automatically. Please > provide the issue details directly (such as title, description, > reproduction steps, or expected vs. actual behavior) so we can proceed."
Pliki w paczce (3)
- SKILL.md 4 KB
- scripts/fetch_crbug.py 15 KB
- scripts/fetch_crbug_test.py 20 KB
Wersje
W bazie nie ma innych skilli o nazwie crbug.
Migawka bazy z 13.11.2026 · wersja paczki 5af78d8c2465 (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
- 87github-issues
Czyta i obsługuje zgłoszenia GitHub przez gh CLI, gdy użytkownik poda link do issue albo poprosi o pracę nad zgłoszeniem. - 100issue-investigation
Bada zgłoszenia GitHub projektu mimo2codex: pobiera szczegóły, odtwarza problemy, analizuje przyczyny źródłowe i proponuje rozwiązania. - 100fix-bug
Naprawia zgłoszony błąd w React Router na podstawie zgłoszenia GitHub: pobiera issue, znajduje reprodukcję, pisze nieprzechodzący test i implementuje poprawkę. - 100issue-creation
Generuje zgłoszenia zgodne z szablonami repozytorium GitHub lub GitLab, takie jak raporty błędów i prośby o funkcje. - 100chromium-docs
Przeszukuje lokalny indeks dokumentacji Chromium: dokumenty projektowe, API i przewodniki rozwoju dotyczące architektury, testów, GPU i sieci. - 100drupal-issue
Tworzy, aktualizuje i komentuje zgłoszenia na drupal.org w prowadzonym ręcznym procesie, wraz z wyświetlaniem listy zgłoszeń.