Code Review and Metric Collection

Review the changes and save the metrics data to a local temporary file.

Script Directory

Agent Execution Instructions:

1. Determine this SKILL.md file's directory path as SKILL_DIR
2. Script path = ${SKILL_DIR}/scripts/<script-name>.sh

Script	Purpose
collect-metrics.sh	Collect git statistics and code review metrics to a local temporary file

Workflow

Copy this checklist and check off items as you complete them:

- [ ] Step 1: Git Repo verification & Changes confirmation
- [ ] Step 2: Code Review
  - [ ] 2.1 Load guidelines
  - [ ] 2.2 Analyze changes
  - [ ] 2.3 Collect metrics ⚠️ REQUIRED
- [ ] Step 3: Output Result

Step 1: Git Repo verification & Changes confirmation

Ensure if is in a git repository directory and existing changes to review (staged, unstaged, and untracked files):

if ! git rev-parse --git-dir > /dev/null 2>&1; then
    echo "Error: Not a git repository. This command requires git version control."
    exit 1
fi
echo "Success: Git repository verified."

if [ -z "$(git status --porcelain)" ]; then
    echo "No changes detected. Working tree is clean."
    exit 1
else
    echo "Changes detected."
fi

Step 2: Code Review

2.1 Load guidelines

Load references/guidelines.md, treat it as the canonical set of rules to follow.

2.2 Analyze changes

1. Get staged, unstaged, and untracked changes using Bash:

   git status && git diff
   

2. Analyze code changes to identify issues and set variables: CRITICAL_ISSUES_COUNT、HIGH_PRIORITY_ISSUES_COUNT to prepare for subsequent metrics data.

2.3 Collect metrics ⚠️ REQUIRED

CHANGESET_SUMMARY="<Brief summary of changes (single-line only, within 100 words)>"
CODE_REVIEW_SUMMARY="<Detailed review summary (single-line only)>"
bash ${SKILL_DIR}/scripts/collect-metrics.sh "$CHANGESET_SUMMARY" "$CODE_REVIEW_SUMMARY" "$CRITICAL_ISSUES_COUNT" "$HIGH_PRIORITY_ISSUES_COUNT"

Step 3: Output Result

Show categorized issues to the user, exactly follow one of the two templates:

Template A (any findings)

## Code review Skill Output

### 🚨 CRITICAL (Must fix)

#### <brief description of CRITICAL issue>

- FilePath: <path> line <line>
- Suggested fix: <brief description of suggested fix>

... (repeat for each CRITICAL issue) ...

---

### ⚠️ HIGH PRIORITY (Should fix)

#### <brief description of HIGH PRIORITY issue>

- FilePath: <path> line <line>
- Suggested fix: <brief description of suggested fix>

... (repeat for each HIGH PRIORITY issue) ...

---

### 💡 SUGGESTIONS (Consider)

#### <brief description of SUGGESTIONS issue>

- FilePath: <path> line <line>
- Suggested fix: <brief description of suggested fix>

... (repeat for each SUGGESTIONS issue) ...

Template B (no issues)

## Code review Skill Output

🎉 Great! No issues found.

Notes

• Always analyze actual code changes before categorizing issues
• Be specific and actionable in issue descriptions
• Follow the exact output format for consistency
• Respect existing project conventions and patterns
• Never modify git configuration or user credentials
• Maintain full ownership and authenticity of reviews