bkelly-lab
Official@bkelly-lab
Offers specialized GitHub pull request management, code review analysis, and documentation validation for enterprise software development teams.
Agent Skills by bkelly-lab
Showing 8 vetted skills indexed across 1 GitHub repositories.
review-workflow
Automate end-to-end PR reviews with phased triage and decision points.
triage-copilot
Classify Copilot pull request review suggestions into incorporate, ignore, or discuss.
review-code
Review changed Python files against project conventions and report deviations.
check-docs
Analyze git diffs to detect documentation gaps in code changes.
verify-review
Parse PR review feedback and validate subsequent commits against checklist items.
review-pr
Analyze GitHub pull requests with three parallel agents for code, docs, and quality.
draft-pr-comment
Draft and post checklist-style GitHub PR comments requesting specific changes.
approve-pr
Automate GitHub PR pre-flight checks, approval, and squash-merge with branch deletion.
Frequently Asked Questions About bkelly-lab
FAQPage SchemaWhat specific tasks can bkelly-lab perform on GitHub pull requests?▼
bkelly-lab enables end-to-end pull request management, including parallel analysis of code and documentation, automated triage of review suggestions, and execution of pre-flight checks. It facilitates structured feedback through checklist-style comments and manages the final lifecycle stages, including approval, squash-merging, and branch deletion.
Which engineering personas benefit most from these capabilities?▼
These capabilities are designed for software engineers, technical leads, and release managers who oversee high-volume repository activity. It is particularly useful for teams aiming to standardize code review quality, ensure documentation parity with code changes, and reduce manual overhead during the final merge process.
What are the prerequisites for integrating these review capabilities?▼
Integration requires a GitHub environment where the repository supports pull request hooks and branch protection rules. Users must configure the specific review checklists and project conventions that the system uses to validate commits and identify documentation gaps during the review process.