New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Dakota Review

by projectbluefin in projectbluefin/dakota

Review Dakota pull requests and work with issues, data-donation reports, labels, and contributor workflow.

MITAuto-check passedDevelopment

Install Dakota Review

skills CLI
$ npx skills add projectbluefin/dakota --skill dakota-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install projectbluefin/dakota dakota-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/projectbluefin/dakota.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dakota-review .claude/skills/dakota-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dakota-review
GitHub stars
180
Token cost
~936 tokens
SKILL.md length
428 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Review Dakota pull requests and work with issues, data-donation reports, labels, and contributor workflow.

  • Works in 5 steps: Verify Target Branch: Ensure PR targets… → Review Hygiene & Commits → Inspect Implementation → …
  • Tasks that involve Pull requests
  • SKILL.md covers When to Use, When NOT to Use, Core Process and Invariants, plus 4 more sections
  • Calls just

What it does

Dakota Review is an agent skill from projectbluefin/dakota. Review Dakota pull requests and work with issues, data-donation reports, labels, and contributor workflow.

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: The buildstream for making Bluefin. The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/dakota-review”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Verify Target Branch: Ensure PR targets testing (or next if explicitly tracking rolling), never main.
  2. Review Hygiene & Commits
  3. Inspect Implementation
  4. Evaluate Evidence
  5. Constructive Feedback

What it can do on your machine

Read from SKILL.md and the folder at commit 909f687. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • just

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dakota Review loads about 936 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 428 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~30
When it runs · the whole SKILL.md, loaded when a task matches
~936

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from projectbluefin/dakota at commit 909f687, republished under its MIT licence (© projectbluefin). 428 words, ~936 tokens.

Download SKILL.mdSave it as .claude/skills/dakota-review/SKILL.md (or your agent's skills folder).
name
dakota-review
description
Review Dakota pull requests and work with issues, data-donation reports, labels, and contributor workflow.

Dakota Review and Issue Workflow

Review pull requests and issues with high discipline: minimal diff, correct target branch, evidence-based verification, and strict boundaries.

When to Use

  • Performing code or architecture reviews on PRs in projectbluefin/dakota
  • Triaging issues, user-donated diagnostic gists (ujust report), or verification comments
  • Enforcing contributor guidelines, PR checklists, and commit hygiene

When NOT to Use

  • Writing code changes or authoring elements → load dakota-buildstream or dakota-packaging
  • Modifying release promotion or signing gates → load dakota-release
  • Authoring CI workflows → load dakota-ci

Core Process

  1. Verify Target Branch: Ensure PR targets testing (or next if explicitly tracking rolling), never main.
  2. Review Hygiene & Commits:
    • Check commit format: <type>(<scope>): <description>.
    • Ensure commits use Assisted-by:, never Co-authored-by:.
  3. Inspect Implementation:
    • Ensure image changes use BuildStream elements (no DNF, RPMs, or Containerfiles).
    • Ensure layer additions use kind: compose (never kind: stack).
    • Check that third-party GitHub Actions are pinned to full commit SHAs.
  4. Evaluate Evidence:
    • For bugs, check for attached gists from ujust report.
    • Verify that claimed test results were actually executed (just validate, just boot-test, etc.).
  5. Constructive Feedback:
    • If asked to post feedback, compose at most one concise, actionable comment.
    • Never restate GitHub UI status (e.g. "checks are passing").

Invariants

  • PROHIBITION ON ublue-os/*: Never write to any ublue-os/* repository under any circumstance. Ask a human to report upstream manually.
  • Commit Trailer Invariant: Use Assisted-by:, never Co-authored-by:.
  • Target Branch: PRs must target testing. main is a release bookmark.
  • Hardware Evidence Priority: verified: N/3 on issues is post-ship proof that cannot be substituted by CI. Do not close bugs without hardware verification or explicit maintainer direction.
  • Communication Etiquette: Do not post automated comments or review messages unless explicitly commanded by the user.
Show full SKILL.md (151 more words)Show less

Common Rationalizations

RationalizationReality
"I should post a comment acknowledging the PR is open."Unrequested agent comments create noise. Post only when explicitly instructed.
"The PR targets main, but that's fine since it's the default branch on some repos."main is a protected release bookmark in Dakota. Merging into it breaks release tracking. PRs must target testing.
"Co-authored-by: is standard GitHub syntax."Dakota repository policy strictly mandates Assisted-by:.

Red Flags

  • Pull requests with Co-authored-by: trailers in commit messages
  • PRs targeting main instead of testing
  • Suggesting fixes or workarounds inside ublue-os/* repositories
  • Closing an issue with report: attached without checking the gist
  • Restating check statuses or queue positions in review comments

Verification

  • Target branch is confirmed as testing
  • Commit messages follow conventional standards and use Assisted-by:
  • No RPM, DNF, or Containerfile overlays introduced
  • Layer elements use kind: compose
  • just validate has been confirmed locally or in CI

References

© projectbluefin, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/dakota-review of projectbluefin/dakota.

Open the folder on GitHubat commit 909f687

Compare with similar skills

Dakota Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dakota Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dakota Review this skillprojectbluefin/dakota180—~936Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    91k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from projectbluefin/dakota

All 10 skills in this repo

  • Dakota Buildstream

    projectbluefin/dakota

    BuildStream elements, junctions, patches, dependency graphs, and build failures in Dakota.

    180 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Dakota Extensions

    projectbluefin/dakota

    Package, update, and configure GNOME Shell extensions, Quick Settings panels, and schemas in Dakota.

    180 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Dakota Factory

    projectbluefin/dakota

    Maintain task-relevant Dakota guidance: documentation accuracy, official-source verification, and skill auditing.

    180 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Dakota Packaging

    projectbluefin/dakota

    Add, remove, or update native software built from source in Dakota, including Go, Rust, Zig, C/Meson, and binary releases.

    180 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Dakota Ujust

    projectbluefin/dakota

    Author safe end-user ujust recipes in files/just-overrides/default.just, including quoting, gum, JSON, and public-post confirmation.

    180 GitHub stars~1.1k tokensUpdated today
    Auto-check: notes

  • Dakota Image

    projectbluefin/dakota

    OCI layer assembly, boot testing, installer boundaries, VM work, and local OTA verification for Dakota images.

    180 GitHub stars~929 tokensUpdated today
    Auto-check passed

Categories

Questions about Dakota Review

What does Dakota Review do?

Review Dakota pull requests and work with issues, data-donation reports, labels, and contributor workflow. Dakota Review is an agent skill from projectbluefin/dakota. Review Dakota pull requests and work with issues, data-donation reports, labels, and contributor workflow.

When should I use Dakota Review?

Dakota Review fits situations like: tasks that involve Pull requests.

How do I install Dakota Review in Claude Code?

Run `npx skills add projectbluefin/dakota --skill dakota-review -a claude-code`. Or copy the skill folder (.agents/skills/dakota-review in projectbluefin/dakota) into .claude/skills/dakota-review in your project. Claude Code loads it when a task matches its description.

How do I install Dakota Review in Codex?

Run `npx skills add projectbluefin/dakota --skill dakota-review -a codex`. Or copy the skill folder (.agents/skills/dakota-review in projectbluefin/dakota) into .agents/skills/dakota-review in your project. Codex loads it when a task matches its description.

Can I use Dakota Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add projectbluefin/dakota --skill dakota-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dakota-review, .gemini/skills/dakota-review, .github/skills/dakota-review and .opencode/skills/dakota-review in your project.

What does Dakota Review need to run?

Going by SKILL.md and its folder, Dakota Review needs the command-line tools its instructions call (just).

Does Dakota Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Dakota Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dakota Review use?

Dakota Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dakota Review use?

About 936 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dakota Review?

Skills that share tags, products or a category with Dakota Review: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 91k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dakota Review?

projectbluefin (a GitHub organization) maintains it in projectbluefin/dakota, which has 180 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 10, 2026.

Source: projectbluefin/dakota on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.