Commit Graph

4 Commits

Author SHA1 Message Date
Surponess b1db102e9d 修改仓库内容 2026-07-10 10:55:03 +08:00
林迪文 d478de59a3 feat: 新增 6 个 Agent Skill + 收窄 gitlink-search 触发范围
新增 Skill:
- gitlink-onboarding: 新人入门引导,帮助新贡献者发现适合入门的 Issue
- gitlink-issue-triage: Issue 智能分拣,按类型/紧急度/复杂度分类并生成分拣报告
- gitlink-research-tracker: 技术调研报告生成,多维度评估+成熟度评分+趋势洞察
- gitlink-contributor-insight: 贡献者活跃度分析,支持命令可用性降级适配
- gitlink-ci-health: CI 健康巡检,通过 repo +info 检测 DevOps 状态
- gitlink-notification-digest: 通知摘要,支持 source 字段分类和批量已读

修改:
- gitlink-search: 收窄描述避免与 research-tracker 触发冲突

每个 Skill 均包含使用示例。

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-03 10:36:13 +08:00
wbtiger 90dee6eeb5 fix(skills): add tool boundary rules to prevent gh/hub misuse on GitLink
Problem:
AI agents (e.g., Claude Code) sometimes use `gh` (GitHub CLI) instead of
`gitlink-cli` when operating on GitLink repositories, causing 'command not
found' errors or targeting the wrong platform.

Solution:
- Add ' Tool Boundary' section to gitlink-shared/SKILL.md with platform-
  to-tool mapping table, judgment criteria, and dual-platform guidance
- Add CRITICAL one-liner to all 10 sub-skills ensuring agents see the
  constraint even without reading shared
- Does NOT block `gh` for GitHub operations — only prevents misuse on
  GitLink resources

Tested with 5 scenarios confirming:
1. GitLink operations correctly use gitlink-cli
2. GitHub operations still use gh when appropriate
3. Ambiguous cases default to gitlink-cli when skill is loaded
2026-04-18 16:14:20 +08:00
wbtiger e892370de8 init gitlink-cli 2026-04-17 10:01:30 +08:00