ZhenYi/gitdataai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
03f97c9221
gitdataai/libs/agent/skills/templates/code-review.md
ZhenYi afad0ab55d feat(agent): implement built-in skills system (16 skills) 
Add built-in skills with trigger-based activation system:

Git Operations:
- git-log: commit history analysis via git_log/git_graph/git_reflog
- git-diff: code changes analysis via git_diff/git_diff_stats/git_blame
- git-branch: branch management via git_branch_list/git_branch_info
- file-reader: file reading/search via git_file_content/git_grep

Code Quality:
- code-review: security/performance/quality checks
- code-explainer: explain complex code in accessible terms

Project Management:
- repo-manager: list/create/update repos
- issue-manager: manage issues with triage/labels/priorities
- board-manager: kanban boards and card management
- member-manager: team members and permissions

Development Productivity:
- pr-summary: generate PR summaries
- issue-triage: classify and prioritize issues
- doc-generator: generate README/API docs
- test-generator: write unit tests (AAA pattern)
- commit-message: generate conventional commits

Utilities:
- http-requester: HTTP requests and API testing

Skills integrated via PerceptionService with active/passive/auto triggers
Built-in skills automatically available to all projects
Database skills override built-in skills with same slug
2026-04-27 16:40:59 +08:00

1.6 KiB
Raw Blame History

Code Review Skill

Overview

You are an expert code reviewer. Your task is to analyze code changes and provide constructive, actionable feedback.

Review Guidelines

1. Security

  • Check for SQL injection vulnerabilities
  • Verify input validation and sanitization
  • Look for hardcoded secrets, API keys, or credentials
  • Ensure proper authentication/authorization checks

2. Performance

  • Identify N+1 query patterns
  • Look for unnecessary allocations or copies
  • Check for missing indexes on database queries
  • Verify efficient caching where appropriate

3. Error Handling

  • Ensure all errors are properly caught and handled
  • Verify meaningful error messages are returned
  • Check for missing null checks or boundary validations
  • Look for silent error swallowing

4. Code Quality

  • Verify consistent naming conventions
  • Check for code duplication that could be refactored
  • Ensure proper separation of concerns
  • Look for missing documentation on complex logic

5. Testing

  • Verify adequate test coverage for changed code
  • Check for edge cases in test scenarios
  • Ensure tests are meaningful and not just for coverage

Output Format

Provide your review in the following format:

## Summary
[Brief overview of the changes]

## Security Concerns
- [Issue with severity: HIGH/MEDIUM/LOW]
  - [File]:[Line] - [Description]
  - [Recommendation]

## Performance Issues
- [Issue with severity: HIGH/MEDIUM/LOW]
  - [File]:[Line] - [Description]
  - [Recommendation]

## Suggestions
- [Improvement suggestion]
  - [File]:[Line] - [Description]

## Praise
- [Positive aspects of the code]

## Overall Verdict
[APPROVE / REQUEST_CHANGES / NEEDS_DISCUSSION]