crowi-complete-feature

Validates worktree changes against objective gates and signals readiness for merge.

1.1k|165|Updated Aug 18, 2014
One-click install
npx skills add https://github.com/crowi/crowi --skill crowi-complete-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crowi-complete-feature
Source: https://github.com/crowi/crowi/tree/main/.claude/skills/crowi-complete-feature
Command: npx skills add https://github.com/crowi/crowi --skill crowi-complete-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working in parallel git worktrees, it is hard to know whether a feature branch is truly done and safe to merge. This Skill runs an objective gate suite (clean tree, commits present, type-check, tests, lint, OpenAPI drift, e2e) and only marks the task as READY_TO_INTEGRATE when every gate passes, giving the orchestrator a trustworthy merge signal.

Core Features & Use Cases

  • Objective gate execution: Runs git status, type-check, unit tests, lint, OpenAPI drift checks, and a helper-driven e2e gate, refusing to signal readiness if anything fails.
  • Task state signaling: Updates or synthesizes .feature-state/tasks/{id}.json via task-state.sh so the main-session orchestrator can pick up the ready-for-merge signal.
  • Flaky test triage: Re-runs failed test gates in isolation to distinguish flaky failures from real ones, and reports flakiness to the manager via agmsg without blocking the gate.
  • Use Case: After finishing a bug fix directly on a worktree branch without a spec, run this Skill to synthesize a task record and flag it READY_TO_INTEGRATE so the orchestrate watcher merges it.

Quick Start

Ask the AI to run the crowi-complete-feature skill in the current worktree to verify all gates and mark the task ready for merge.

Frequently Asked Questions about crowi-complete-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I mark a worktree branch as ready for merge?

Run the crowi-complete-feature skill inside the worktree after finishing implementation and QA. It executes gates for clean tree, commits, type-check, tests, lint, OpenAPI, and e2e, then sets the task status to READY_TO_INTEGRATE only when all pass.

What happens if a task file does not exist for my branch?

The skill synthesizes a task record from git history instead of aborting. It derives the name, commits, and context from git log, then creates the task via task-state.sh so the orchestrator can still pick up the ready signal.

How does the skill handle flaky test failures?

Failed test gates are re-run in isolation with reduced parallelism. If the isolated run passes, the full suite is re-run once and the manager is notified via agmsg; the gate only blocks if the full re-run still fails.

Can I run this skill on the main branch?

No. The skill aborts immediately if the current branch is main, since it is designed to run inside a feature worktree. It also never merges to main or pushes; those steps belong to the orchestrator and user.

What happens when e2e infrastructure is down?

If docker-based mongo or redis is unavailable, the skill treats it as blocked rather than failed. It reports 'blocked: e2e infra down', does not set the ready signal, and asks you to restart the infrastructure and re-run.