skills.rest
jsco2t
jsco2tCOMMUNITY
Explore all skills by this author →
GitHub

ww-code-reviewer

Automate pre-PR code reviews for Warewulf projects with DCO, formatting, and linting fixes.

1|Updated Jun 7, 2024
Search Tags:#formatting#lint#code-review#pr-review#dco#warewulf
One-click install
npx skills add https://github.com/jsco2t/dotfiles --skill ww-code-reviewer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ww-code-reviewer
Source: https://github.com/jsco2t/dotfiles/tree/main/.claude/skills/ww-code-reviewer
Command: npx skills add https://github.com/jsco2t/dotfiles --skill ww-code-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Warewulf PRs often require extensive manual checks. The ww-code-reviewer skill automates the pre-PR review process by identifying and fixing issues that community reviewers typically flag, reducing back-and-forth and speeding up merge readiness.

Core Features & Use Cases

  • Automated Checks: Validate DCO sign-off, Go formatting, and linting/vet steps to ensure code quality before submission.
  • Automated Fixes: Proactively apply safe fixes where possible and clearly flag items that require user intervention.
  • Scope-aware Review: Compare changes against main by default and adjust scope based on user input (branch, files, or scope) to tailor reviews.

Quick Start

Run the code reviewer against your current branch to automatically detect and fix common Warewulf PR issues.

Frequently Asked Questions about ww-code-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Warewulf PR review checks for DCO sign-off and Go formatting?▼

Automate Warewulf PR review checks by validating DCO sign-off, Go formatting, and linting against your feature branch and main, reducing manual back-and-forth. The skill detects common issues and applies safe auto-fixes before submission.

What is the best way to fix lint and vet errors before submitting a Warewulf PR?▼

Fix lint and vet errors by running an automated pre-review against your local diff or feature branch. The process applies safe auto-corrections for Go tooling issues and clearly flags items requiring manual intervention to speed up merge readiness.

Do I need Go tooling and git history access to run automated Warewulf code reviews?▼

Yes, automated Warewulf code reviews require access to git history and Go tooling, including lint and vet suites. These dependencies are necessary to compare branch changes and execute automated formatting and linting corrections.

Can I scope automated code reviews to specific files instead of a full branch diff?▼

Yes, you can scope automated code reviews by adjusting the input parameters. The review defaults to comparing changes against main but can be tailored to analyze specific files, branches, or custom scopes based on your input.

Why does my Warewulf pull request keep getting flagged by reviewers for formatting issues?▼

Warewulf pull requests get flagged for formatting when Go code is not properly linted or vetted before submission. Automating pre-PR checks applies safe fixes to formatting and linting issues, ensuring code quality standards are met prior to review.

Related Skills

Explore More Software Engineering Skills→
gopherguidesgopherguides
19

go-code-review

Analyze Go PR diffs to generate inline review comments, quality scores, and breaking change alerts.

Official
Advanced
nikhilsitaramnikhilsitaram
89

pr-merge

Merge reviewed GitHub pull requests and clean up branches and worktrees.

Community
Advanced
muratmirgunmuratmirgun
8

go-code-review

Review Go diffs with severity-labeled findings and rule citations.

Community
Advanced
ulpi-ioulpi-io
13

claude-review

Spawn a Claude Code agent in an isolated worktree to review code changes.

Official
Advanced