brave/brave-core
14 skills97 installs48.6k starsGitHub
Install
npx skills add https://github.com/brave/brave-coreSkills in this repo
1Impl ReviewThis skill implements reviewer feedback on a brave-core pull request. A developer uses it to check out a PR's branch, apply exactly the changes reviewers requested, run preflight checks, commit, and push. It fetches all review and issue comments, presents a plan for confirmation, makes only the requested changes as new commits, and posts a summary comment.8installs2Add Best PracticeThis skill adds a new best practice rule to the appropriate brave-core best-practices document. A developer uses it to capture a guideline (often from a GitHub PR review comment) in the correct category doc with no duplicates and a stable ID. It reads the actual source code behind a review comment, drafts the entry in the exact existing format, and runs a review subagent to validate accuracy before writing.7installs3Check Upstream FlakeThis skill checks whether a failing test is a known upstream flake in Chromium's LUCI Analysis database. A developer uses it when investigating intermittent test failures or evaluating test-disable PRs, to see historical flakiness statistics before deciding on a fix. It queries the public LUCI Analysis REST API and reports a verdict and recommendation for filter-file decisions.7installs4Clean BranchesThis skill cleans up local git branches by checking each branch's GitHub PR status and deleting those that have been merged. A developer uses it to prune branches after PRs land, including squash-merged ones that ancestry checks miss. It detects merges via direct ancestry, git cherry patch-equivalence, and gh PR status, then categorizes branches and asks for confirmation before deleting.7installs5Fix Bp DocsThis skill audits and fixes the brave-core best-practices documentation for stale references, duplicates, obsolete content, and formatting issues. A developer uses it to keep the docs accurate as the codebase evolves, verifying that referenced brave/ and Chromium file paths and symbols still exist. It fixes duplicates while preserving anchor IDs, checks the index, and validates IDs at the end.7installs6Force Push DownstreamThis skill force-pushes a branch and all of its downstream branches to their remotes. A developer uses it when managing a stacked chain of dependent branches that need pushing together after a rebase. It auto-detects the downstream tree, skips branches whose local and remote tips already match, uses --force-with-lease for safety, and asks for confirmation before pushing.7installs7Make Ci GreenRe-runs failed Jenkins CI jobs for a brave/brave-core pull request. It detects the failure stage and decides between a normal re-run for flaky test failures and a WIPE_WORKSPACE re-run for build or infrastructure failures. It also analyzes test failures to flag whether they came from the PR or are known upstream flakes. A developer uses it after CI goes red to retrigger only the failing checks.7installs8PrCreates a pull request for the current branch using the GitHub CLI. It reviews the branch commits and changed files, checks for an associated GitHub issue, pushes the branch, and opens the PR with a short title and a factual body. A developer uses it to turn finished branch work into a PR without hand-writing the description.7installs9PreflightRuns all preflight checks on the current brave-core work to make sure it is ready for review. It executes format, gn_check, presubmit, build, and the affected test suites in sequence and stops immediately if any step fails. A developer runs it before opening a PR to catch formatting, build, and test problems locally.7installs10Rebase DownstreamRebases a tree of dependent branches after upstream changes. It auto-detects the downstream branch chain including siblings, rebases each branch onto its parent with --fork-point, resolves conflicts where possible, and runs preflight checks on every branch. A developer uses it to propagate changes through a stack of feature branches.7installs11ReviewReviews code changes for quality, root-cause analysis, and fix confidence. It supports a local mode over the current branch diff and a PR mode by URL or number, detecting the correct base branch and reading modified files for context. In PR mode it researches previous fix attempts and fails the review if the current fix is not materially different. A developer uses it to vet a change or a bot-authored PR before merge.7installs12Top CrashersQueries Brave's Backtrace crash-reporting instance for the top crashers. It returns developer-actionable data including crash signatures, stack traces, platform and version breakdowns, channel mapping, code-origin classification, and triage URLs, and can detect new or rising regressions. Only aggregate PII-safe data is output. A developer uses it to prioritize which crashes to fix after a release.7installs13Prs ReviewedQueries GitHub for the pull requests a user has reviewed on brave/brave-core within a time window. It searches by reviewer, verifies each review timestamp falls in range, and presents a table of PR number, title, author, state, and review date. A developer or lead uses it for standups and review-workload analysis.6installs14Review PrsScans recent pull requests in a configured repository for violations of documented best practices. It runs a file-based pipeline where prepare and collect scripts do the heavy fetching with zero LLM tokens and subagents review each diff, then posts capped inline review comments. It offers an interactive mode that asks for approval and an auto mode for cron. A developer or bot uses it to enforce best practices across a PR queue.6installs