gitea-workflow by jwynia/agent-skills
npx skills add https://github.com/jwynia/agent-skills --skill gitea-workflow一个通过智能顺序调用命令,引导代理完成 Gitea 仓库结构化敏捷开发工作流的技能。使用基于检查点的流程控制,在步骤间自动推进,并在关键决策点暂停。
在以下情况使用此技能:
在以下情况不要使用此技能:
/status)/review-code)使用此技能前,需满足:
tea login)context-network/backlog/ 处具有待办事项结构广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
context-network/backlog/by-status/*.mdWORKFLOW TYPES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TASK CYCLE (Primary) DAILY SPRINT
────────────────────── ────────────────── ──────────────────
sync Morning: Start:
↓ sync --last 1d sync --all
next → [CHECKPOINT] status --brief groom --all
↓ groom --ready plan sprint-goals
implement status
↓ Evening:
[CHECKPOINT] checklist End:
↓ discovery sync --sprint
review-code sync --last 1d retrospective
review-tests audit --sprint
↓ maintenance --deep
[CHECKPOINT]
↓
apply-recommendations (if issues)
↓
pr-prep → [CHECKPOINT]
↓
pr-complete
↓
update-backlog & status
↓
END
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
该技能自动确定当前工作流状态。无需手动跟踪。
| 信号 | 如何检查 | 指示 |
|---|---|---|
| 工作树存在 | git worktree list | 任务进行中 |
| 任务分支处于活动状态 | git branch --show-current 匹配 task/* | 活动实现中 |
| 未提交的更改 | git status --porcelain | 活动编码中 |
| PR 存在 | tea pulls list --state open | 审查中 |
| PR 已合并 | tea pulls + 检查状态 | 准备清理 |
STATE DETECTION LOGIC
─────────────────────────────────────────────────────────────
Check → State → Next Step
─────────────────────────────────────────────────────────────
No worktree, no in-progress → IDLE → sync, next
Worktree exists, uncommitted → IMPLEMENTING → continue implement
Worktree exists, all committed → READY_REVIEW → review-code
PR open, CI pending → AWAITING_CI → wait or address
PR open, CI pass → READY_MERGE → pr-complete
PR merged, worktree exists → CLEANUP → pr-complete
─────────────────────────────────────────────────────────────
有关详细的检测算法,请参阅 references/state-detection.md。
# 自动检测状态并从当前位置继续
/gitea-workflow
# 启动特定工作流阶段
/gitea-workflow --phase task-cycle
/gitea-workflow --phase daily-morning
/gitea-workflow --phase daily-evening
/gitea-workflow --phase sprint-start
/gitea-workflow --phase sprint-end
# 恢复处理特定任务
/gitea-workflow --task TASK-123
# 预览将要执行的操作而不实际执行
/gitea-workflow --dry-run
完成单个任务(从选择到合并)的主要工作流。
确保上下文网络与实际项目状态匹配。
Run: sync --last 1d --dry-run
Purpose: Detect drift between documented and actual state
Output: Sync report showing completions, partial work, divergences
确定下一个要处理的任务。
Run: next
Purpose: Find highest priority ready task
Output: Task ID, title, branch name suggestion
检查点:TASK_SELECTED
在隔离的工作树中进行测试驱动开发。
Run: implement [TASK-ID]
Purpose: Create worktree, write tests first, implement, verify
Output: Working implementation with passing tests
检查点:IMPL_COMPLETE
对实现进行质量验证。
Run: review-code --uncommitted
Run: review-tests --uncommitted
Purpose: Identify quality issues, security concerns, test gaps
Output: Review reports with issues and recommendations
检查点:REVIEWS_DONE
智能处理审查发现的问题。
Run: apply-recommendations [review-output]
Purpose: Apply quick fixes now, defer complex changes to tasks
Output: Applied fixes + created follow-up tasks
创建包含完整文档的拉取请求。
Run: pr-prep
Purpose: Validate, document, and create PR
Output: PR created with description, tests verified
检查点:PR_CREATED
合并并进行清理。
Run: pr-complete [PR-NUMBER]
Purpose: Merge PR, delete branch, remove worktree, update status
Output: Task marked complete, cleanup done
将进度持久化到单一事实来源文档。
Run: Part of pr-complete (Phase 6)
Purpose: Update epic file (task → complete), unblock dependents, update project status
Output: Backlog and project status reflect actual progress
此步骤的重要性: 如果没有此步骤,已完成的任务在待办事项文件中仍标记为"就绪",项目状态也会过时。内部跟踪文件是会话范围的;待办事项和状态文件是持久化的单一事实来源。
有关详细的任务周期说明,请参阅 references/phases/task-cycle.md。
工作日开始和结束时的快速序列。
Run sequence:
1. sync --last 1d --dry-run # What actually happened yesterday
2. status --brief --sprint # Current sprint health
3. groom --ready-only # What's ready to work on
Output: Clear picture of today's priorities
Run sequence:
1. checklist # Ensure nothing lost
2. discovery # Capture learnings
3. sync --last 1d # Update task statuses
Output: Knowledge preserved, state synchronized
有关详细的每日说明,请参阅 references/phases/daily.md。
冲刺边界仪式。
Run sequence:
1. sync --all # Full reality alignment
2. groom --all # Comprehensive grooming
3. plan sprint-goals # Architecture and goals
4. status --detailed # Baseline metrics
Output: Sprint plan with groomed, ready backlog
Run sequence:
1. sync --sprint # Final sprint sync
2. retrospective # Capture learnings
3. audit --scope sprint # Quality review
4. status --metrics # Sprint metrics
5. maintenance --deep # Context network cleanup
Output: Sprint closed, learnings captured, ready for next
有关详细的冲刺说明,请参阅 references/phases/sprint.md。
检查点是用于人工决策的暂停点。
在每个检查点:
| 响应 | 操作 |
|---|---|
| "continue" / "proceed" / "yes" | 进入下一步 |
| "stop" / "pause" | 保存状态,退出工作流 |
| "back" | 重新运行上一步 |
| "skip" | 跳过当前步骤(谨慎使用) |
| 自定义输入 | 可能调整下一步参数 |
某些检查点在满足条件时可以自动继续:
| 检查点 | 自动继续条件 |
|---|---|
| IMPL_COMPLETE | 所有测试通过,构建成功 |
| REVIEWS_DONE | 没有关键或高严重性问题 |
| PR_CREATED | CI 通过(通过 API 验证),获得所需批准 |
有关详细的检查点处理,请参阅 references/checkpoint-handling.md。
每个工作流步骤都使用嵌入的命令指令:
| 命令 | 参考 | 目的 |
|---|---|---|
| sync | references/commands/sync.md | 现实同步 |
| groom | references/commands/groom.md | 任务细化 |
| next | references/commands/next.md | 任务选择 |
| implement | references/commands/implement.md | TDD 实现 |
| review-code | references/commands/review-code.md | 代码质量审查 |
| review-tests | references/commands/review-tests.md | 测试质量审查 |
| apply-recommendations | references/commands/apply-recommendations.md | 分类并应用修复 |
| pr-prep | references/commands/pr-prep.md | PR 创建 |
| pr-complete | references/commands/pr-complete.md | PR 合并与清理 |
| discovery | references/commands/discovery.md | 学习捕获 |
| retrospective | references/commands/retrospective.md | 事后分析 |
| maintenance | references/commands/maintenance.md | 上下文网络清理 |
场景: 一天开始,实现下一个可用任务
调用:
/gitea-workflow --phase task-cycle
流程:
Agent: Detecting current state...
No worktree found, checking ready tasks...
Agent: Running sync --last 1d --dry-run
[Sync output: 0 tasks completed but undocumented]
Agent: Running next
Found: TASK-042 - Add user preferences endpoint
Priority: High | Size: Small | Branch: task/TASK-042-preferences
╔═══════════════════════════════════════════╗
║ CHECKPOINT: Task Selection ║
╠═══════════════════════════════════════════╣
║ Selected: TASK-042 ║
║ Proceed with implementation? ║
║ ║
║ [continue] [stop] [other task] ║
╚═══════════════════════════════════════════╝
User: continue
Agent: Creating worktree at .worktrees/TASK-042/
Running implement TASK-042
[Implementation proceeds with TDD...]
Tests: 12 passing
Coverage: 87%
Build: Success
╔═══════════════════════════════════════════╗
║ CHECKPOINT: Implementation Complete ║
╠═══════════════════════════════════════════╣
║ All tests passing, ready for review ║
║ Proceed to code review? ║
║ ║
║ [continue] [stop] ║
╚═══════════════════════════════════════════╝
[Flow continues through review, PR, merge...]
Gitea 使用外部 CI 系统(Drone、Woodpecker、Jenkins 等)。要检查 CI 状态:
scripts/gitea-ci-status.sh 查询提交状态| 操作 | Tea CLI 命令 |
|---|---|
| 列出打开的 PR | tea pulls list --state open |
| 创建 PR | tea pulls create --title "..." --description "..." --base main --head branch |
| 查看 PR | tea pulls |
| 合并 PR(压缩) | tea pulls merge --style squash |
| 合并 PR(合并) | tea pulls merge --style merge |
| 合并 PR(变基) | tea pulls merge --style rebase |
| 批准 PR | tea pulls approve |
| 列出议题 | tea issues list |
对于 tea CLI 中不可用的操作,请使用提供的 API 脚本:
scripts/gitea-ci-status.sh - 通过 Gitea API 检查 CI 状态scripts/gitea-pr-checks.sh - 获取 PR 审查/批准状态tea CLI 进行 PR 操作)每周安装数
112
仓库
GitHub 星标数
37
首次出现
2026年2月2日
安全审计
安装于
codex102
opencode101
gemini-cli99
github-copilot99
kimi-cli96
amp95
A skill that guides agents through structured agile development workflows for Gitea repositories by intelligently invoking commands in sequence. Uses checkpoint-based flow control to auto-progress between steps while pausing at key decision points.
Use this skill when:
Do NOT use this skill when:
/status directly)/review-code directly)Before using this skill:
tea login)context-network/backlog/context-network/backlog/by-status/*.mdWORKFLOW TYPES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TASK CYCLE (Primary) DAILY SPRINT
────────────────────── ────────────────── ──────────────────
sync Morning: Start:
↓ sync --last 1d sync --all
next → [CHECKPOINT] status --brief groom --all
↓ groom --ready plan sprint-goals
implement status
↓ Evening:
[CHECKPOINT] checklist End:
↓ discovery sync --sprint
review-code sync --last 1d retrospective
review-tests audit --sprint
↓ maintenance --deep
[CHECKPOINT]
↓
apply-recommendations (if issues)
↓
pr-prep → [CHECKPOINT]
↓
pr-complete
↓
update-backlog & status
↓
END
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The skill determines current workflow state automatically. No manual tracking needed.
| Signal | How to Check | Indicates |
|---|---|---|
| Worktree exists | git worktree list | Task in progress |
| Task branch active | git branch --show-current matches task/* | Active implementation |
| Uncommitted changes | git status --porcelain | Active coding |
| PR exists | tea pulls list --state open | In review |
| PR merged |
STATE DETECTION LOGIC
─────────────────────────────────────────────────────────────
Check → State → Next Step
─────────────────────────────────────────────────────────────
No worktree, no in-progress → IDLE → sync, next
Worktree exists, uncommitted → IMPLEMENTING → continue implement
Worktree exists, all committed → READY_REVIEW → review-code
PR open, CI pending → AWAITING_CI → wait or address
PR open, CI pass → READY_MERGE → pr-complete
PR merged, worktree exists → CLEANUP → pr-complete
─────────────────────────────────────────────────────────────
For detailed detection algorithms, see references/state-detection.md.
# Auto-detect state and continue from where you are
/gitea-workflow
# Start specific workflow phase
/gitea-workflow --phase task-cycle
/gitea-workflow --phase daily-morning
/gitea-workflow --phase daily-evening
/gitea-workflow --phase sprint-start
/gitea-workflow --phase sprint-end
# Resume work on specific task
/gitea-workflow --task TASK-123
# Preview what would happen without executing
/gitea-workflow --dry-run
The primary workflow for completing a single task from selection to merge.
Ensure context network matches actual project state.
Run: sync --last 1d --dry-run
Purpose: Detect drift between documented and actual state
Output: Sync report showing completions, partial work, divergences
Identify the next task to work on.
Run: next
Purpose: Find highest priority ready task
Output: Task ID, title, branch name suggestion
CHECKPOINT: TASK_SELECTED
Test-driven development in isolated worktree.
Run: implement [TASK-ID]
Purpose: Create worktree, write tests first, implement, verify
Output: Working implementation with passing tests
CHECKPOINT: IMPL_COMPLETE
Quality validation of implementation.
Run: review-code --uncommitted
Run: review-tests --uncommitted
Purpose: Identify quality issues, security concerns, test gaps
Output: Review reports with issues and recommendations
CHECKPOINT: REVIEWS_DONE
Address review findings intelligently.
Run: apply-recommendations [review-output]
Purpose: Apply quick fixes now, defer complex changes to tasks
Output: Applied fixes + created follow-up tasks
Create pull request with full documentation.
Run: pr-prep
Purpose: Validate, document, and create PR
Output: PR created with description, tests verified
CHECKPOINT: PR_CREATED
Merge and cleanup.
Run: pr-complete [PR-NUMBER]
Purpose: Merge PR, delete branch, remove worktree, update status
Output: Task marked complete, cleanup done
Persist progress to source-of-truth documentation.
Run: Part of pr-complete (Phase 6)
Purpose: Update epic file (task → complete), unblock dependents, update project status
Output: Backlog and project status reflect actual progress
Why this step matters: Without it, completed tasks remain marked "ready" in backlog files and project status stays stale. Internal tracking files are session-scoped; the backlog and status files are the persistent source of truth.
For detailed task-cycle instructions, see references/phases/task-cycle.md.
Quick sequences for start and end of workday.
Run sequence:
1. sync --last 1d --dry-run # What actually happened yesterday
2. status --brief --sprint # Current sprint health
3. groom --ready-only # What's ready to work on
Output: Clear picture of today's priorities
Run sequence:
1. checklist # Ensure nothing lost
2. discovery # Capture learnings
3. sync --last 1d # Update task statuses
Output: Knowledge preserved, state synchronized
For detailed daily instructions, see references/phases/daily.md.
Ceremonies for sprint boundaries.
Run sequence:
1. sync --all # Full reality alignment
2. groom --all # Comprehensive grooming
3. plan sprint-goals # Architecture and goals
4. status --detailed # Baseline metrics
Output: Sprint plan with groomed, ready backlog
Run sequence:
1. sync --sprint # Final sprint sync
2. retrospective # Capture learnings
3. audit --scope sprint # Quality review
4. status --metrics # Sprint metrics
5. maintenance --deep # Context network cleanup
Output: Sprint closed, learnings captured, ready for next
For detailed sprint instructions, see references/phases/sprint.md.
Checkpoints are pauses for human decision-making.
At each checkpoint:
| Response | Action |
|---|---|
| "continue" / "proceed" / "yes" | Move to next step |
| "stop" / "pause" | Save state, exit workflow |
| "back" | Re-run previous step |
| "skip" | Skip current step (use cautiously) |
| Custom input | May adjust next step parameters |
Some checkpoints can auto-continue when conditions are met:
| Checkpoint | Auto-Continue If |
|---|---|
| IMPL_COMPLETE | All tests pass, build succeeds |
| REVIEWS_DONE | No critical or high severity issues |
| PR_CREATED | CI passes (verified via API), required approvals obtained |
For detailed checkpoint handling, see references/checkpoint-handling.md.
Each workflow step uses embedded command instructions:
| Command | Reference | Purpose |
|---|---|---|
| sync | references/commands/sync.md | Reality synchronization |
| groom | references/commands/groom.md | Task refinement |
| next | references/commands/next.md | Task selection |
| implement | references/commands/implement.md | TDD implementation |
| review-code | references/commands/review-code.md | Code quality review |
| review-tests |
Scenario: Start of day, implement next available task
Invocation:
/gitea-workflow --phase task-cycle
Flow:
Agent: Detecting current state...
No worktree found, checking ready tasks...
Agent: Running sync --last 1d --dry-run
[Sync output: 0 tasks completed but undocumented]
Agent: Running next
Found: TASK-042 - Add user preferences endpoint
Priority: High | Size: Small | Branch: task/TASK-042-preferences
╔═══════════════════════════════════════════╗
║ CHECKPOINT: Task Selection ║
╠═══════════════════════════════════════════╣
║ Selected: TASK-042 ║
║ Proceed with implementation? ║
║ ║
║ [continue] [stop] [other task] ║
╚═══════════════════════════════════════════╝
User: continue
Agent: Creating worktree at .worktrees/TASK-042/
Running implement TASK-042
[Implementation proceeds with TDD...]
Tests: 12 passing
Coverage: 87%
Build: Success
╔═══════════════════════════════════════════╗
║ CHECKPOINT: Implementation Complete ║
╠═══════════════════════════════════════════╣
║ All tests passing, ready for review ║
║ Proceed to code review? ║
║ ║
║ [continue] [stop] ║
╚═══════════════════════════════════════════╝
[Flow continues through review, PR, merge...]
Gitea uses external CI systems (Drone, Woodpecker, Jenkins, etc.). To check CI status:
scripts/gitea-ci-status.sh to query commit statuses| Operation | Tea CLI Command |
|---|---|
| List open PRs | tea pulls list --state open |
| Create PR | tea pulls create --title "..." --description "..." --base main --head branch |
| View PR | tea pulls |
| Merge PR (squash) | tea pulls merge --style squash |
| Merge PR (merge) | tea pulls merge --style merge |
| Merge PR (rebase) | tea pulls merge --style rebase |
For operations not available in the tea CLI, use the provided API scripts:
scripts/gitea-ci-status.sh - Check CI status via Gitea APIscripts/gitea-pr-checks.sh - Get PR review/approval statustea CLI for PR operations)Weekly Installs
112
Repository
GitHub Stars
37
First Seen
Feb 2, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
codex102
opencode101
gemini-cli99
github-copilot99
kimi-cli96
amp95
Azure Data Explorer (Kusto) 查询技能:KQL数据分析、日志遥测与时间序列处理
130,600 周安装
tea pulls + check state |
| Ready for cleanup |
| references/commands/review-tests.md |
| Test quality review |
| apply-recommendations | references/commands/apply-recommendations.md | Triage and apply fixes |
| pr-prep | references/commands/pr-prep.md | PR creation |
| pr-complete | references/commands/pr-complete.md | PR merge and cleanup |
| discovery | references/commands/discovery.md | Learning capture |
| retrospective | references/commands/retrospective.md | Post-work analysis |
| maintenance | references/commands/maintenance.md | Context network cleanup |
| Approve PR | tea pulls approve |
| List issues | tea issues list |