القائمة
Get PRs a user reviewed on brave/brave-core. Shows PR number, title, author, state, and links. Triggers on: prs reviewed, reviewed prs, review activity, what did I review, review history.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Create a Plaster (`rewrite/*.yaml`) config for an existing Brave-core Chromium `.patch`, authoring an intent-conveying regex match per the Plaster Dos and Don'ts, then verifying it by running `plaster.py apply` and diffing the regenerated patch against the original. Does not modify sources or create other files. Triggers on: plaster from patch, convert patch to plaster, plasterize, make a plaster.
For an external contributor's open PRs to brave/brave-core, ensure the `sync-and-rebase-pr-from-fork.yml` workflow has been dispatched for each PR's latest commit SHA — so a `contributor-*` draft PR exists inside brave/brave-core and CI can run. Invoke when the user says something like "create contributor PRs for <user>", "sync contributor PRs <list>", "run the rebase-from-fork workflow for these PRs", or passes a GitHub username / list of PR URLs/numbers.
Add a new best practice to the appropriate doc. Checks for duplicates, assigns stable IDs, creates new category docs if needed. Triggers on: add best practice, new best practice, add bp, new bp.
"Create an uplift PR that cherry-picks merged PRs from a contributor into a target branch (beta or release). Defaults to broad eligibility; the scope can be narrowed via a free-form description (e.g. 'only automated test and crash fixes'). Triggers on: /uplift, create uplift, uplift PRs."
Review PRs in the configured PR repository for best practices violations. Supports single PR (#12345), state filter (open/closed/all), and auto mode for cron. Triggers on: review prs, review recent prs, /review-prs, check prs for best practices.
Run all preflight checks (format, gn_check, presubmit, build, tests) to make sure the current work is ready for review.
استنادا إلى تصنيف SOC المهني
| name | prs-reviewed |
| description | Get PRs a user reviewed on brave/brave-core. Shows PR number, title, author, state, and links. Triggers on: prs reviewed, reviewed prs, review activity, what did I review, review history. |
| argument-hint | <username> <num>d |
| disable-model-invocation | true |
Query GitHub for pull requests a user has reviewed on brave/brave-core within
a given time window.
The skill receives arguments in the format: <username> <num>d
<username> — GitHub username (e.g., netzenbot)<num>d — Number of days to look back from now (e.g., 3d means last 3 days)Both arguments are required. If missing, ask the user for them.
Calculate the start date by subtracting <num> days from today's date, then use
the GitHub CLI to search for reviewed PRs:
gh api --paginate "search/issues?q=type:pr+repo:brave/brave-core+reviewed-by:<username>+updated:>%3D<YYYY-MM-DD>&per_page=100" --jq '.items[] | {number, title, user: .user.login, state, pull_request: .pull_request.html_url, updated_at}'
Where <YYYY-MM-DD> is the computed start date.
Important: The updated:>= filter is a rough filter. After fetching
results, you must verify each PR was actually reviewed by the user within the
requested window by checking review timestamps:
gh api "repos/brave/brave-core/pulls/<number>/reviews" --jq '[.[] | select(.user.login == "<username>")] | sort_by(.submitted_at) | last | .submitted_at'
Only include PRs where the user's most recent review falls within the requested time window.
Display results in a markdown table:
| PR | Title | Author | State | Reviewed |
|---|---|---|---|---|
| #1234 | Fix crash in ... | author | merged | 2026-02-25 |
[#number](html_url) formatpull_request.merged_at to
distinguish merged from closed)Sort by review date, most recent first.
After the table, show a summary: "N PRs reviewed by @username in the last Md"
gh is not authenticated, inform the user to run gh auth login