[PR #6365] [CLOSED] [PM-30849] Simplify code-review command to use reviewing-changes skill #25901

Closed
opened 2026-04-17 01:30:11 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/6365
Author: @SaintPatrck
Created: 1/15/2026
Status: Closed

Base: context-rulesHead: devclarity/update-code-review-command


📝 Commits (1)

  • 00bf96b refactor(claude): Simplify code-review command to use reviewing-changes skill

📊 Changes

1 file changed (+10 additions, -73 deletions)

View changed files

📝 .claude/commands/code-review.md (+10 -73)

📄 Description

🎟️ Tracking

PM-30849

📔 Objective

Note

Additional prep for DevClarity training. Builds upon #6364.

Simplify the code-review command by delegating the core logic to the new reviewing-changes skill.

The previous verbose template, which included detailed instructions and a complex output format for manual reviews, has been removed. The new implementation directly invokes the reviewing-changes skill with the pull request URL.

Specific changes include:

  • Replaced the extensive review template in .claude/commands/code-review.md with a simpler command definition.
  • The command now accepts a PR URL as its primary argument.
  • It is explicitly defined to use the reviewing-changes skill for the review process.
  • Output requirements are now specified to be written to pr-review-summary.md and pr-review-inline-comments.md.

📸 Screenshots

Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/6365 **Author:** [@SaintPatrck](https://github.com/SaintPatrck) **Created:** 1/15/2026 **Status:** ❌ Closed **Base:** `context-rules` ← **Head:** `devclarity/update-code-review-command` --- ### 📝 Commits (1) - [`00bf96b`](https://github.com/bitwarden/android/commit/00bf96bcd4fde0855386c2692324c74feebaadce) refactor(claude): Simplify code-review command to use `reviewing-changes` skill ### 📊 Changes **1 file changed** (+10 additions, -73 deletions) <details> <summary>View changed files</summary> 📝 `.claude/commands/code-review.md` (+10 -73) </details> ### 📄 Description ## 🎟️ Tracking PM-30849 ## 📔 Objective > [!NOTE] > Additional prep for DevClarity training. Builds upon #6364. Simplify the `code-review` command by delegating the core logic to the new `reviewing-changes` skill. The previous verbose template, which included detailed instructions and a complex output format for manual reviews, has been removed. The new implementation directly invokes the `reviewing-changes` skill with the pull request URL. Specific changes include: - Replaced the extensive review template in `.claude/commands/code-review.md` with a simpler command definition. - The command now accepts a PR URL as its primary argument. - It is explicitly defined to use the `reviewing-changes` skill for the review process. - Output requirements are now specified to be written to `pr-review-summary.md` and `pr-review-inline-comments.md`. ## 📸 Screenshots <!-- Required for any UI changes; delete if not applicable. Use fixed width images for better display. --> ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Protected functional changes with optionality (feature flags) - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-17 01:30:11 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#25901