Review git branch diffs for logical errors, edge cases, and documentation freshness.
npx skills add https://github.com/crbnos/carbon --skill self-review-crbnos
Please help me install this Agent Skill. Skill: self-review Source: https://github.com/crbnos/carbon/tree/main/.ai/skills/self-review Command: npx skills add https://github.com/crbnos/carbon --skill self-review-crbnos
This Skill unit ensures the quality and maintainability of your code by providing a thorough review of your branch work before merging into the main branch.
Run the 'self-review' skill on your branch to review your code changes and generate a report on issues and documentation updates.
High-intent search queries and answers about installing and using this skill.
To review code commits for logical errors before merging a branch, you can analyze the branch diff against main to detect bugs, identify missing edge cases, and resolve code inefficiencies.
A branch diff check evaluates code maintainability by reviewing commits for inefficiencies, while simultaneously scanning the changes to ensure all relevant documentation is complete and up-to-date.
Yes, you can use an automated code review to find missing edge cases in your software development process by analyzing the full branch diff to pinpoint logical errors and potential bugs.
The best way to ensure code quality before opening a pull request is to run a comprehensive review on your branch work to audit code logic, verify documentation freshness, and confirm overall maintainability.
Yes, you need a git diff to perform a quality assurance audit on your branch, as generating a branch diff against the main branch is required to evaluate the commits and detect code inefficiencies.
chrisliu298Remove AI-generated commentary and dead code from git diffs.
stu43005Verify test passes, present merge or PR options, and clean up branches.
aaddrickLint shell scripts with shellcheck and GitHub Actions workflows with actionlint.
IndustrialAnalyze code for security vulnerabilities and performance issues.
