review-commit

Review Swift file diffs for bugs and commit staged changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Mp2025-cmd/ScrollKitty --skill review-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-commit
Source: https://github.com/Mp2025-cmd/ScrollKitty/tree/main/.claude/skills/review-commit
Command: npx skills add https://github.com/Mp2025-cmd/ScrollKitty --skill review-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of reviewing code changes for bugs and then committing them with a descriptive, project-aligned message, ensuring code quality and consistent commit history.

Core Features & Use Cases

  • Automated Bug Detection: Leverages a specialized agent (ios-swift-bug-finder) to scan modified Swift files for potential bugs.
  • Guided Commit Process: Provides clear steps for inspecting diffs, checking for bugs, and crafting commit messages according to project conventions.
  • Use Case: After making several changes to a Swift file, you can use this Skill to automatically check for common bugs, ensure the commit message follows the project's style, and add the necessary co-author line.

Quick Start

Use the review-commit skill to inspect the current git diff, check for bugs in Swift files, and then commit the changes with a descriptive message.

Frequently Asked Questions about review-commit

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

FAQPage Schema
How do I check my Swift code for bugs before creating a git commit?

To check Swift code for bugs before a git commit, you can automate the process by scanning changed files for deterministic errors and then generating a project-aligned commit message with co-author attribution.

Can I automatically generate a commit message that follows my project conventions?

Yes, you can automatically generate a commit message that follows project conventions by inspecting staged git diffs and crafting a concise message aligned with established repository styles.

What is the best way to find bugs in modified Swift files during a code review?

The best way to find bugs in modified Swift files during a code review is using a specialized bug finder agent to scan git diffs for deterministic issues before committing changes.

Does this automated code review and commit process work for non-Swift programming languages?

This automated code review and commit process is designed specifically for Swift files, utilizing a dedicated bug finder agent to scan modified files for deterministic issues.

How do I add co-author attribution to my git commits automatically?

To add co-author attribution to git commits automatically, you can use a guided commit process that crafts concise messages and appends the necessary co-author line according to project conventions.

What are the limitations of using an automated Swift bug finder for git commits?

The limitation of using an automated Swift bug finder for git commits is that it focuses on deterministic bug checking in modified files, meaning it may not catch complex logic errors outside of its scanning scope.