Eleven-MEleven-M/flowmind/skills/git-review/SKILL.md

git-review

Skill1 starsChanged 3 months agoMITView on GitHub

Git repository and commit review skill for FlowMind. Review commit history, analyze changes, and ensure code quality.

2 other projects use a version of this.

Adopted by

Most recently taken up by

gitByEOS/open-part-skillstheir own version, first seen Nov 2, 2026
dkubb/skillstheir own version, first seen Oct 14, 2026

Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
gitByEOS/open-part-skills★ 38same name
dkubb/skills★ 14same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- api-syncSkill
- archive-changeSkill
- auto-flowSkill
- build-reportSkill
- change-impact-reviewSkill
- code-review-auditSkill
- code-reviewSkill
- coverage-reportSkill
- data-logic-validationSkill
- data-risk-auditSkill
- data-validationSkill
- dingtalk-notifySkill
- knowledge-opsSkill
- learning-engineSkill
- learning-feedbackSkill
- log-auditSkill
- offline-design-analysisSkill
- project-reviewSkill
- release-inspectionSkill
- report-insightsSkill
- requirement-analystSkill
- resource-bindSkill
- service-governance-auditSkill
- service-governance-changeSkill
- service-governance-diagnosisSkill
- service-management-log-analysisSkill
- sls-log-auditSkill
- test-reportSkill
- yapi-sync-interfaceSkill
- yuque-sync-designSkill

The file

Create a free account to mount

Files

SKILL.md

Git Review Skill

Review commit history, analyze changes, and ensure code quality.

Features

📊 Commit Analysis

Commit message quality
Change size analysis
Author statistics
Time patterns

🔍 Change Review

Diff analysis
Impact assessment
Risk evaluation
Dependency changes

📈 Quality Metrics

Code churn rate
Review coverage
Test coverage
Documentation updates

Trigger Patterns

"git审查", "git review"
"提交历史", "commit history"
"代码变更", "code changes"
"分支审查", "branch review"
"PR审查", "PR review"

Output Format

┌─────────────────────────────────────────────────────┐
│ Git Review Report                                   │
├─────────────────────────────────────────────────────┤
│ Branch: {branch}                                    │
│ Commits: {count}                                    │
│ Files Changed: {files}                              │
│ Lines: +{added} -{removed}                          │
├─────────────────────────────────────────────────────┤
│ Commit Quality:                                     │
│ ✓ Good: {good_count}                                │
│ ⚠ Warning: {warn_count}                             │
│ ✗ Bad: {bad_count}                                  │
├─────────────────────────────────────────────────────┤
│ Issues:                                             │
│ • {issue_description}                               │
└─────────────────────────────────────────────────────┘

Commit Quality Checks

Message Quality

Check	Description
Format	Follows conventional commits
Length	Subject < 50 chars, body < 72 chars
Clarity	Descriptive and clear
Reference	Links to issues/PRs

Change Quality

Check	Description
Size	Commits not too large
Scope	Single responsibility
Tests	Includes test changes
Docs	Documentation updated

Learning Integration

This skill supports FlowMind learning:

Review Focus: Learns what to check first
Severity Levels: Learns your standards
Output Format: Learns preferred report format

User: "先检查提交规范"
FlowMind: ✓ Learned: Check commit conventions first

User: [Next review]
FlowMind: [Prioritizes commit conventions]

Examples

Example 1: Branch Review

User: 审查 feature/login 分支

FlowMind:
┌─────────────────────────────────────────────────────┐
│ Git Review Report                                   │
├─────────────────────────────────────────────────────┤
│ Branch: feature/login                               │
│ Commits: 12                                         │
│ Files Changed: 23                                   │
│ Lines: +1,847 -234                                  │
├─────────────────────────────────────────────────────┤
│ Commit Quality:                                     │
│ ✓ Good: 10                                          │
│ ⚠ Warning: 2                                        │
├─────────────────────────────────────────────────────┤
│ Warnings:                                           │
│ • abc123: "fix stuff" - Too vague                   │
│ • def456: Large commit (500+ lines)                 │
├─────────────────────────────────────────────────────┤
│ Impact:                                             │
│ • Authentication: Major changes                     │
│ • Database: New migration                           │
│ • API: 5 new endpoints                              │
└─────────────────────────────────────────────────────┘

Example 2: Commit History

User: 查看最近的提交历史

FlowMind:
┌─────────────────────────────────────────────────────┐
│ Recent Commits                                      │
├─────────────────────────────────────────────────────┤
│ 2026-06-22 15:30 - feat: add OAuth2 login          │
│ 2026-06-22 14:20 - fix: resolve session timeout     │
│ 2026-06-22 11:45 - docs: update API documentation   │
│ 2026-06-21 18:00 - refactor: optimize queries       │
│ 2026-06-21 16:30 - test: add login tests            │
├─────────────────────────────────────────────────────┤
│ Statistics:                                         │
│ • 5 commits by 2 authors                            │
│ • 3 features, 1 fix, 1 docs                         │
│ • +456 -89 lines                                    │
└─────────────────────────────────────────────────────┘

Configuration

{
  "git-review": {
    "checks": {
      "commitMessage": true,
      "changeSize": true,
      "testCoverage": true,
      "documentation": true
    },
    "limits": {
      "maxCommitLines": 500,
      "maxCommitFiles": 20
    }
  }
}

Commit Message Convention

<type>(<scope>): <subject>

[optional body]

[optional footer]

Types:

feat: New feature
fix: Bug fix
docs: Documentation
style: Formatting
refactor: Code refactoring
test: Adding tests
chore: Maintenance

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free