review-and-ship

Assess branch changes for quality and test coverage, then prepare a pull request.

58|5|Updated Aug 30, 2024
One-click install
npx skills add https://github.com/StudyDrift/lextures --skill review-and-ship-studydrift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-and-ship
Source: https://github.com/StudyDrift/lextures/tree/main/.cursor/skills/review-and-ship
Command: npx skills add https://github.com/StudyDrift/lextures --skill review-and-ship-studydrift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing code branches to identify bugs, validate intent alignment, and ensure adequate test coverage is time-consuming and error-prone without a repeatable process.

Core Features & Use Cases

  • Automated branch assessment: quickly evaluates diffs for bug risks, alignment with goals, and coverage gaps.
  • Targeted testing workflow: suggests or runs tests to verify changes and pinpoints required additions.
  • PR readiness: helps prepare a focused commit, push, and PR with concise summaries and verifiable results.

Quick Start

Review the current branch for issues, ensure tests pass, and prepare a PR with focused changes.

Frequently Asked Questions about review-and-ship

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

FAQPage Schema
How do I automate code review and test coverage checks before opening a pull request?

Automated code review evaluates your current branch diff to assess bug risks, intent alignment, and test coverage gaps. It coordinates diff analysis with recent commits to ensure correctness and safe PR submission.

What is the best way to analyze uncommitted changes and recent commits for bug risks?

Analyzing uncommitted changes involves assessing branch diffs for bug risks and intent alignment. This process coordinates diff analysis, recent commits, and changed files to validate branch correctness.

How do I write targeted tests for changed files in a git workflow?

Writing targeted tests for changed files involves assessing coverage gaps in your current branch. The workflow suggests or runs specific tests to verify changes and pinpoints required additions.

Can I prepare focused commits and push updates for a pull request automatically?

Preparing focused commits and pushing updates for a pull request involves assessing diff impact and test coverage. It helps commit focused changes and open or update a PR with concise summaries.

Does this branch assessment workflow work without external testing dependencies?

Branch assessment works without external dependencies. It analyzes the current branch internally to identify changes, assess their impact on intent and quality, and run or write targeted tests as needed.

When should I not use automated PR readiness checks for my code changes?

Automated PR readiness checks are not ideal for branches requiring manual intent validation outside of diff analysis. The process focuses on coordinating changed files, recent commits, and test coverage for safe submission.