REPO PACKAGE
brave brave-core
OFFICIAL17skills
1ready to use
LABSCO SUMMARY
The skills cover the full loop of shipping a change to brave/brave-core: creating and rebasing branches (clean-branches, force-push-downstream, rebase-downstream), opening and updating pull requests (pr, create-contributor-prs, impl-review), getting CI green (preflight, make-ci-green, check-upstream-flake), and reviewing others' work (review, review-prs, prs-reviewed). A separate pair, plaster-from-patch and add-best-practice/fix-bp-docs, handle Chromium patch authoring and the team's internal best-practices documentation. One skill, top-crashers, pulls live crash data from Brave's own Backtrace reporting service.
This only serves someone with commit access to brave/brave-core who is already working inside Brave's own branch-and-review workflow — build tooling for Chromium, GitHub PR automation, and an internal crash dashboard. It has nothing for someone building a browser extension, customizing Brave, or using the browser itself; the actual product documentation lives in the linked brave-browser repository and the docs folder, not in any of these seventeen skills.
READ THE FULL ANALYSIS
The public README says nothing about any of this. It documents what the repository is — build tooling that fetches and patches Chromium — and points elsewhere for issues, releases, and the wiki. It does not mention skills, this folder, or that seventeen of them ship here.
WHAT'S INSIDE
17 showing · 17 totalReady to use
Nothing else to set up — install it and go.
17 of 17
SETUP
Showing all 17 skills
add-best-practice
Writes a new team coding rule into the project's own best-practices docs — checking first that nobody has already written the same rule, and giving it a permanent number others can link to.
check-upstream-flake
A test just failed — is that your doing, or does the test fail at random for everyone? This looks the test up in Chromium's public record of past runs and answers with real numbers.
clean-branches
Deletes the leftover copies of finished work sitting on your own machine, after checking with GitHub that each one really did make it into the project.
create-contributor-prs
Code sent in by outsiders doesn't get Brave's full run of automated tests, for safety reasons; this makes an in-house copy of each submission so those tests can run on it after all.
fix-bp-docs
Goes through the team's written coding rules and repairs what has rotted — the same rule written twice, examples pointing at files that were renamed or deleted, links that lead nowhere.
force-push-downstream
Work that sits in a stack, each piece built on the one below it, gets uploaded to the shared copy in one pass — with anything already up there left alone.
impl-review
Someone reviewed your code and asked for changes; this makes exactly those changes and nothing more, answers the questions they raised, runs the checks, and pushes the result back.
make-ci-green
When a change's automated checks come back red, this decides which failures just need another run, which need the build machine wiped clean, and which have nothing to do with your change.
plaster-from-patch
Brave's edits to Chromium sit in patch files that break whenever the upstream code shifts; this rewrites one of them as a search-and-replace rule that survives, then proves it reproduces the original exactly.
pr
Pushes the branch you are working on up to GitHub and opens its pull request, so a finished change gets in front of reviewers without a separate write-up step.
preflight
Runs every check a change has to pass before anyone else looks at it — formatting, the build, the project's own pre-submission rules, the tests — and stops at the first one that fails.
prs-reviewed
Turns one person's review history on Brave's main code repository into a dated table — which changes they looked at, who wrote them, and whether those changes made it in.
rebase-downstream
Change something that other unfinished work is built on, and all of that work has to be rebuilt on top of it — this does that piece by piece, in the right order, running the checks on each one.
review
Judges a code change on whether it really addresses the cause of the problem rather than the symptom, checks it against the team's written rules, and ends on a plain pass or fail.
review-prs
Sweeps through the change requests waiting in a repository, checks each one against the team's written rules, and drafts the comments — for you to approve, or posted on their own on a schedule.
top-crashers
A ranked list of what is crashing the Brave browser out in the world — where each crash happens, which platforms and versions it hits, and whether it is new — with no personal user data in it.
uplift
Carries one contributor's recently merged fixes over into the beta or release version of the Brave browser, gathering them into a single pull request and chasing up the tracking issue each one is supposed to have.
No skill in this package matches that.
HOW TO GET IT
WHOLE PACKAGEInstall the whole package (17 skills)
npx skills add brave/brave-coreSINGLE SKILLOr install a single skill
npx skills add brave/brave-core --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.