Compare feature branches against develop and generate Mermaid architecture diagrams and PR review checklists.
npx skills add https://github.com/tykisgod/quick-question --skill brief-tykisgod
Please help me install this Agent Skill. Skill: brief Source: https://github.com/tykisgod/quick-question/tree/main/skills/brief Command: npx skills add https://github.com/tykisgod/quick-question --skill brief-tykisgod
Game development teams using Unity, Godot, Unreal, or S&box often spend hours manually reviewing branch changes against the develop branch, risking missed critical architectural shifts and inconsistent review quality. This Skill automates the process, delivering clear, structured review documentation to speed up code reviews and catch high-risk changes early.
Use the brief skill to compare your current feature branch against the develop branch and generate the architecture review and PR checklist documents.
High-intent search queries and answers about installing and using this skill.
To generate a PR checklist for C# game development branches, compare your feature branch against the develop branch. This automatically categorizes architectural changes into impact tiers and outputs a prioritized review checklist with specific risk descriptions for every changed file.
Yes, you can automatically generate Mermaid architecture diagrams from git diffs. The tool analyzes branch differences to create module dependency, data flow, state machine, and class relationship diagrams with color-coded annotations for new, modified, and deleted components.
Yes, this code review tool supports Unity, Godot, Unreal, and S&box projects. It is specifically designed to analyze C# code modifications across these game development platforms to identify high-risk cross-module contract changes and new subsystems.
The best way to identify high-risk architectural changes is using tiered architecture change analysis. This automatically classifies modifications into cross-module contracts, new subsystems, internal refactoring, and configuration changes to highlight the most critical modifications first.
Prioritized items in an automated PR review checklist are structured into three tiers: P0 for must-human-review, P1 for recommended attention, and P2 for quick scan. Each tier provides specific risk descriptions and review guidance for the changed files.
selfagencyAnalyze git status and diff to create Git Flow branches.
jame2408Analyzes code diffs from pull requests to generate intent summaries, logic walkthroughs, and Mermaid architecture diagrams.
Totes-MickGOATsImplement state machine patterns in Unity for game logic and AI.
icartshAnalyze .NET solutions for code quality, security, and dependency issues.
