Brave Experiments
Official@brave-experiments · United States of America
Engineering infrastructure for Chromium-based browser development, focusing on Git branch management, pull request lifecycle, and technical documentation integrity.
Agent Skills by Brave Experiments
Showing 24 vetted skills indexed across 2 GitHub repositories.
brave-experimentsadd-best-practice
Add new best practice entries to Markdown files with unique IDs.
brave-experimentsprs-reviewed
Retrieve GitHub pull requests reviewed by a user on brave/brave-core.
brave-experimentsimpl-review
Implement code review feedback on pull requests with automated validation.
brave-experimentsforce-push-downstream
Force-push a Git branch and its downstream dependency tree to origin.
brave-experimentscheck-best-practices
Audit local branch changes against best practices documentation for C++, tests, frontend, Android, iOS, and build files.
brave-experimentsfix-bp-docs
Audit and correct best practices markdown for stale references and duplicates.
brave-experimentscommit
Create atomic Git commits with descriptive messages and optional branch creation.
brave-experimentstop-crashers
Retrieve and analyze top crashers from Brave's Backtrace system.
brave-experimentscheck-milestones
Correct and synchronize GitHub PR and issue milestones by merge branch.
brave-experimentscheck-upstream-flake
Query Chromium LUCI Analysis for test flakiness statistics and verdicts.
brave-experimentslearnable-pattern-search
Extract learnable coding patterns from GitHub pull request review comments.
brave-experimentsprd-clean
Archive merged and invalid user stories from prd.json to prd.archived.json.
brave-experimentsrebase-downstream
Rebases dependent Git branches in order after upstream changes with conflict resolution and preflight checks.
brave-experimentspr
Create a GitHub pull request for the active branch using the gh CLI.
brave-experimentsadd-backlog-to-prd
Fetch open GitHub issues by labels or assignee and add missing ones to a PRD backlog.
brave-experimentsuplift
Create uplift pull requests by cherry-picking test and crash fixes from closed PRs.
brave-experimentsmake-ci-green
Re-runs failed Chelimba CI jobs for a specified pull request number in the brave/brave-core repository.
brave-experimentsreview
Review code changes and validate root cause analysis for pull requests.
brave-experimentsprd
Generate Product Requirements Documents in Markdown with user stories and technical specifications.
brave-experimentsclean-branches
Delete local Git branches whose pull requests are merged upstream.
brave-experimentsupdate-best-practices
Insufficient data for an AI-generated response. Please provide the missing information.
brave-experimentsprd-json
Converts natural language PRDs into structured prd.json for brave-core-bot.
brave-experimentspreflight
Run preflight checks for formatting, GN, presubmit, and build.
brave-experimentsreview-prs
Review pull requests in brave/brave-core for best practice violations.
Frequently Asked Questions About Brave Experiments
FAQPage SchemaWhat specific tasks are enabled by these browser development utilities?▼
These utilities enable atomic Git commit creation, automated branch cleanup, cherry-picking crash fixes for uplift, and auditing code against C++, Android, and iOS best practices. They also facilitate the conversion of natural language requirements into structured JSON and manage the synchronization of GitHub milestones and pull request reviews.
Which engineering personas benefit from these repository management skills?▼
These skills are designed for Chromium-based browser engineers, release managers, and technical leads working within the brave-core ecosystem. They specifically support developers tasked with maintaining complex downstream branch trees, ensuring CI stability, and enforcing rigorous documentation standards across large-scale browser codebase contributions.
What are the primary dependencies for executing these browser development tasks?▼
Execution requires a local environment configured for the brave-core repository, including access to GitHub, Chromium LUCI Analysis, and Backtrace systems. Users must have appropriate permissions for the brave/brave-core repository and local installation of standard build environment components like GN and presubmit checkers to perform preflight validations.