gitlink-cli

Commit Graph

Author	SHA1	Message	Date
yetja	4b5d402e89	Merge remote-tracking branch 'origin/master'	2026-07-01 11:48:55 +08:00
yetja	c3fc44cbca	feat: 实现自动化工作流引擎工作流引擎支持5个预置场景（社区运营/代码质量/项目初始化/多仓库协同/贡献者成长）， 3种步骤类型（command/api/skill），2种执行模式（规则引擎/AI增强），以及watch/schedule/daemon三种持续运行模式。 - shortcuts/workflow/: 引擎核心（类型定义、步骤执行器、AI客户端、状态管理、守护进程） - shortcuts/workflow/rules/: 7个确定性规则引擎（triage/health/changelog/review/ci/license/repo） - skills/gitlink-workflow/: 工作流 Skill 文档与示例	2026-07-01 11:42:30 +08:00
Martin	a95b07a507	docs(review): README 智能表登记 gitlink-review，workflow 链回深度审查	2026-06-20 20:24:00 +08:00
yetja	fb5ebc4d2c	完善 repo/org/ci/workflow 四个 AI Agent Skill（SKILL.md + REFERENCE.md + examples）	2026-06-12 19:09:23 +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

6 Commits