Can I choose which review findings to address?

Yes. For every finding, you can choose to FIX it immediately, create a GitHub ISSUE to track it later, or IGNORE it and proceed with the commit.

How does it know my project's specific coding standards?

It automatically discovers and parses rules from CLAUDE.md, .claude/rules/*.md, and CLAUDE.local.md to ensure your changes align with established conventions.

What security checks does this skill perform?

It scans for hardcoded secrets, injection vulnerabilities (SQL/XSS), missing authentication checks, PII exposure in logs, and insecure dependencies.

Does it work with GitHub issues specifically?

Yes, it uses the GitHub CLI (gh) to view ticket context, create follow-up issues for deferred tasks, and post comprehensive summaries back to the original ticket.

Ticket Review & Commit

Name: Ticket Review & Commit
Author: AnExiledDev

byAnExiledDev

•

Collaboration Tools

Performs comprehensive code reviews, verifies requirement fulfillment, and automates structured Git commits and issue tracking.

The Ticket Review & Commit skill provides a rigorous, multi-layered audit of your changes before they enter the codebase. It evaluates staged code against security standards, project-specific rules, architectural patterns, and the original ticket requirements. By automating the discovery of code smells and security risks, and facilitating batch decisions on whether to fix, ignore, or defer issues, it ensures high-quality contributions while generating standardized, context-rich commit messages that maintain perfect traceability with your project management tools.

Key Features

01Multi-dimensional review covering security, architecture, quality, and project-specific rules.

02Interactive decision engine for fixing findings or creating follow-up GitHub issues.

03Automated GitHub issue commenting and cross-referencing for full workflow transparency.

04Automated requirements verification linked directly to GitHub issue descriptions.

05Standardized commit message generation following conventional commits with business context.

066 GitHub stars

Use Cases

01Verifying that all EARS requirements from a ticket are satisfied before final submission.

02Maintaining a standardized, high-quality Git history with detailed technical and business context in every commit.

03Conducting a local security and compliance audit to prevent leaking secrets or violating project standards.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add anexileddev/codeforge ticketreview-commit

For use in Claude.ai and ChatGPT

Download Skill