keel-review-all-day

Automate GitHub code review by scanning commits and creating issues.

4|Updated May 23, 2026
One-click install
npx skills add https://github.com/berkayturanci/keel --skill keel-review-all-day
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: keel-review-all-day
Source: https://github.com/berkayturanci/keel/tree/main/.agents/skills/keel-review-all-day
Command: npx skills add https://github.com/berkayturanci/keel --skill keel-review-all-day

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires keel, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The keel-review-all-day Skill solves the problem of manual code review across a project's history by automating the process of scanning every commit in a merge-window-aligned span, classifying each diff, and creating one GitHub issue per serious finding.

Core Features & Use Cases

  • Automated Code Review: Scan every commit within a specified merge window and classify diffs.
  • Parallel Reviewers: Use parallel reviewers to handle a high number of commits.
  • Issue Creation: Create a GitHub issue for each serious finding.
  • Use Case: Integrate into your development workflow to ensure code quality and identify issues early in the development process.

Quick Start

Run the command /keel:review-all-day <args> to start the review sweep process.

Frequently Asked Questions about keel-review-all-day

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

FAQPage Schema
How do I automate code review across all commits in a GitHub repository?

Automated code review scans every commit in a configurable merge-window-aligned span, classifies diffs using parallel reviewers, and creates a GitHub issue for each serious finding. This replaces manual history sweeps and identifies issues early.

How does automated commit analysis classify and report code issues?

Automated commit analysis classifies diffs by using parallel reviewers to handle a high number of commits within a specified merge window. When serious findings are identified, it automatically creates a corresponding GitHub issue for tracking.

Do I need keel and GitHub API access to run automated commit analysis?

Yes, you need both the keel dependency and GitHub API access to run automated commit analysis. These prerequisites allow the tool to scan repository commits and automatically create GitHub issues for serious findings.

Can I use parallel reviewers to handle a high number of commits in GitHub?

Yes, you can use parallel reviewers to handle a high number of commits during an automated code review. This approach classifies diffs efficiently within a configurable merge-window-aligned span before creating GitHub issues for serious findings.

What is the best way to integrate automated code review into a development workflow?

The best way to integrate automated code review is to run a commit sweep across a configurable merge window. This process classifies diffs with parallel reviewers and generates GitHub issues for serious findings, ensuring code quality early.

How to create GitHub issues automatically from code review findings?

You can create GitHub issues automatically from code review findings by running an automated sweep across commits in a merge-window-aligned span. The tool classifies diffs via parallel reviewers and creates one GitHub issue per serious finding.