From coco
Single-issue workflow for quick fixes and small changes that don't need full epic tracking. Creates a branch, implements the fix, commits with issue tracking, and closes.
npx claudepluginhub skullninja/coco-workflow --plugin cocoThis skill uses the workspace's default tool permissions.
Lightweight workflow for single-issue fixes and small changes that don't warrant full epic tracking.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Lightweight workflow for single-issue fixes and small changes that don't warrant full epic tracking.
For multi-session features with dependencies, use the execute skill instead.
Read .coco/config.yaml for issue tracker configuration.
If $ARGUMENTS contains an issue key/ID, load it. Otherwise, create a new issue:
If "linear":
Use: mcp__plugin_linear_linear__create_issue
Parameters:
title: "{fix description}"
team: {from config issue_tracker.linear.team}
labels: {from config issue_tracker.linear.labels}
state: "In Progress"
If "github":
gh issue create --title "{fix description}" --label "{comma-separated labels from issue_tracker.github.labels in config}"
If github.use_projects is true: check .coco/state/gh-projects.json for an active feature project. If one exists, add the issue to it and set status to "In Progress":
gh project item-add {project_number} --owner {github.owner} --url {issue_url}
gh project item-edit --project-id {project_id} --id {item_id} --field-id {status_field_id} --single-select-option-id {status_options["In Progress"]}
If "none": Skip issue creation.
git checkout -b fix/{short-name}
Check pre_commit.ui_patterns from config against staged files. If matches found and pre-commit-tester agent is configured, invoke it.
git add {specific-files}
git commit -m "$(cat <<'EOF'
{fix description}. Completes {issue_key}
{What was wrong and how it was fixed}
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
Read pr config from .coco/config.yaml.
If pr.enabled:
git push -u origin fix/{short-name}
gh pr create --base main --head fix/{short-name} --title "{issue_key}: {fix description}" --body-file - <<'EOF'
## Fix Summary
{What was wrong and how it was fixed}
Resolves {issue_key}
## Test Results
{test output summary}
EOF
If github.use_projects is true and the issue was added to a project, add the PR to the project board:
gh pr view --json url -q .url
Use the URL from the output:
gh project item-add {project_number} --owner {github.owner} --url "{PR_URL}"
If pr.review.enabled:
code-reviewer agent on the PR/coco:execute)gh pr merge {pr-number} --{pr.issue_merge_strategy} --delete-branch
If pr.enabled is false:
Triggered by PR merge (or by commit if PRs disabled). This is when the issue resolves.
If "linear":
status_map.completed (default: "Done")If "github":
Closes #N in PR body auto-closes the issue (if using PRs)github.use_projects is true and the issue was added to a project: set status to "Done":
gh project item-edit --project-id {project_id} --id {item_id} --field-id {status_field_id} --single-select-option-id {status_options["Done"]}
If "none": Skip
Output: