skills.rest
ncukondo
ncukondoCOMMUNITY
Explore all skills by this author →
GitHub

code-with-task-local

Automate local task implementations with IPC status reporting via .worker-status.json.

5|1|Updated Dec 12, 2025
Search Tags:#git#testing#branch#local#task-management#ipc
One-click install
npx skills add https://github.com/ncukondo/reference-manager --skill code-with-task-local
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-with-task-local
Source: https://github.com/ncukondo/reference-manager/tree/main/.claude/skills/code-with-task-local
Command: npx skills add https://github.com/ncukondo/reference-manager --skill code-with-task-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implements a local task execution workflow without requiring a worktree, enabling isolated task work on an existing branch.

Core Features & Use Cases

  • IPC Status Reporting: writes to the worktree root .worker-status.json with fields branch, task_file, status, current_step, pr_number, error, updated_at.
  • Per-step task workflow: updates status through starting -> in_progress -> testing -> creating_pr -> completed or failed, ensuring traceability and safe progress.
  • PR creation and completion: supports automatic PR creation trigger and records the resulting PR number on completion.

Quick Start

Pick the current task file for your branch and start implementing it locally, updating the IPC status at each step.

Frequently Asked Questions about code-with-task-local

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

FAQPage Schema
How do I track local task implementation status on an existing git branch?▼

Local task implementation status is tracked by writing to a .worker-status.json file in the worktree root, recording fields like branch, task_file, current_step, and updated_at for IPC coordination.

What is the lifecycle for automating task workflow from start to PR creation?▼

The task workflow lifecycle enforces traceable progress through statuses: starting, in_progress, testing, creating_pr, and finally completed or failed, ensuring safe coordination from start to PR creation.

How do I report task progress via IPC for isolated branch work?▼

You report task progress via IPC by updating the .worker-status.json file at each workflow step, allowing external processes to read the current_step and status fields to monitor isolated branch work.

Can I automate PR creation and record the PR number for a local task?▼

Yes, the local task workflow supports an automatic PR creation trigger and records the resulting PR number in the pr_number field of the .worker-status.json file upon task completion.

Do I need a separate worktree to implement tasks locally with IPC status reporting?▼

No, you do not need a separate worktree to implement tasks locally; the workflow enables isolated task work directly on an existing branch while maintaining IPC status reporting.

Why does my local task workflow status get stuck on failed?▼

The local task workflow status moves to failed when an error occurs during execution, logging the specific issue in the error field of the .worker-status.json file for debugging.

Related Skills

Explore More Software Engineering Skills→
lshtramlshtram

start-task

Create isolated git worktree environments with a task.md template.

Community
Intermediate
galfrevngalfrevn
6

triggers

Create, modify, and debug triggers for scheduled tasks, webhooks, and file monitoring.

Community
Intermediate
HenquewlHenquewl
7

finishing-a-development-branch

Verify test suites and finalize git development branches through merge or cleanup.

Community
Advanced
BugRogerBugRoger
4

orchestrator

Manage skill execution phases, dependencies, and parallel subagent tasks.

Community
Advanced