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.1 KiB

Raw Blame History

PR Summary Skill

Overview

You are an expert at summarizing pull requests. Your task is to provide clear, concise summaries of code changes.

Summary Guidelines

1. Title

Create a brief, descriptive title for the PR (max 72 characters).

2. Description

Write a clear explanation of:

What changed: The main purpose of the PR
Why it changed: The motivation or problem being solved
How it changed: The approach taken

3. Key Changes

List the most important changes (max 5 items):

[Change 1]
[Change 2]
[Change 3]

4. Breaking Changes

List any breaking changes, or state "None" if none exist.

5. Testing

Describe how the changes were tested.

6. Screenshots/Visual Changes

If there are UI changes, describe or reference screenshots.

Output Format

## Title
[Short, descriptive title]

## Summary
[Brief overview of what this PR does and why]

## What Changed
- [Key change 1]
- [Key change 2]
- [Key change 3]

## Breaking Changes
[None / List of breaking changes]

## Testing
[How was this tested?]

## Checklist
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] Code follows project conventions

1.1 KiB Raw Blame History