Skip to content

Add initial PR review skills and skill validation hooks. - #9930

Open
kenzieschmoll wants to merge 5 commits into
flutter:masterfrom
kenzieschmoll:review-skills
Open

Add initial PR review skills and skill validation hooks.#9930
kenzieschmoll wants to merge 5 commits into
flutter:masterfrom
kenzieschmoll:review-skills

Conversation

@kenzieschmoll

@kenzieschmoll kenzieschmoll commented Jul 29, 2026

Copy link
Copy Markdown
Member

This PR adds two agent skills to the devtools repo:

  • reviewing-prs: General workflow for fetching, inspecting, reviewing GitHub Pull Requests using the gh CLI, drafting user-aligned review comments, and securing approval before posting. Use when asked to review a GitHub PR or pull request.
  • reviewing-devtools-prs: DevTools repository-specific PR review workflow enforcing DevTools style guidelines and repository rules. Use when reviewing pull requests in the flutter/devtools repository.

These skills should be iterated on over time but they do provide initial value in their current state to help locally reviewing PRs with agents.

This PR also adds two hooks to the devtools repo:

  • run the dart skills linter after any edits to skill files.
  • request that the agent review skill files for best practices after skill file edits.

@kenzieschmoll
kenzieschmoll requested a review from a team as a code owner July 29, 2026 23:22
@kenzieschmoll
kenzieschmoll requested review from bkonyi, johnpryan and srawlins and removed request for a team and bkonyi July 29, 2026 23:22
@kenzieschmoll

Copy link
Copy Markdown
Member Author

CC @pq since this is related to some of the things you are looking at.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces two new markdown files defining workflows for reviewing pull requests: a general PR review workflow (reviewing-prs/SKILL.md) and a DevTools-specific PR review workflow (reviewing-devtools-prs/SKILL.md). The review feedback points out that the relative paths to the style guide, repository constraints, and code style files in the DevTools-specific workflow are incorrect and should be adjusted to reflect the file's directory depth.

Comment on lines +13 to +15
- **Style Guide**: [styleguide.md](../../.gemini/styleguide.md) (severity tags `[MUST-FIX]`, `[CONCERN]`, `[NIT]`, zero-formatting policy, copyright headers, DRY rules, named constants)
- **Repository Constraints**: [AGENTS.md](../../AGENTS.md)
- **Code Style**: [STYLE.md](../../STYLE.md)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

[CONCERN] The relative paths to the style guide, repository constraints, and code style files are incorrect. Since this file is located at .agents/skills/reviewing-devtools-prs/SKILL.md, it is 3 levels deep from the repository root. Therefore, the paths should use ../../../ instead of ../../ to correctly reference these files at the root level.

Suggested change
- **Style Guide**: [styleguide.md](../../.gemini/styleguide.md) (severity tags `[MUST-FIX]`, `[CONCERN]`, `[NIT]`, zero-formatting policy, copyright headers, DRY rules, named constants)
- **Repository Constraints**: [AGENTS.md](../../AGENTS.md)
- **Code Style**: [STYLE.md](../../STYLE.md)
- **Style Guide**: [styleguide.md](../../../.gemini/styleguide.md) (severity tags [MUST-FIX], [CONCERN], [NIT], zero-formatting policy, copyright headers, DRY rules, named constants)
- **Repository Constraints**: [AGENTS.md](../../../AGENTS.md)
- **Code Style**: [STYLE.md](../../../STYLE.md)
References
  1. Prefix every comment with a severity: [MUST-FIX], [CONCERN], [NIT]. (link)

@kenzieschmoll kenzieschmoll Jul 29, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@reidbaker shouldn't dart skills lint catch this?

@kenzieschmoll kenzieschmoll changed the title Add initial PR review skills. Add initial PR review skills and skill validation hooks. Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants