local

Manage issue lifecycles locally with the .issues directory and local-issues CLI.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill local-michael-conrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/issue-operations/platforms/local
Command: npx skills add https://github.com/michael-conrad/.opencode --skill local-michael-conrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a self-contained framework to track, organize, and synchronize issues using a local .issues directory, enabling consistent lifecycle management without mandatory remote collaboration.

Core Features & Use Cases

  • Centralized local issue storage via .issues with frontmatter and structured bodies
  • Full lifecycle workflow including create, update, link, comment, close, push/pull to remote, and promotion
  • Supports worktree mode, cross-repo references, and governance through a robust capability contract and routing rules

Quick Start

Create a local draft issue using the local-issues CLI and manage its lifecycle from draft to promotion or closure.

Frequently Asked Questions about local

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

FAQPage Schema
How do I manage local issue tracking without a mandatory remote platform?

You can manage local issue tracking by using a .issues directory to create, update, and close issues. This framework relies on frontmatter-backed tracking and YAML link graphs to handle the full lifecycle locally.

How does local issue synchronization work with a remote repository?

Local issue synchronization works by using promote, import-remote, push-body, and pull-body commands to sync issues with a remote platform. This keeps your local .issues directory aligned while supporting cross-repo references.

Can I use worktree mode for local issues management?

Yes, worktree mode is supported for local issues management. The workflow includes worktree support, allowing you to create, link, and promote issues directly within isolated git worktrees.

What is the best way to organize cross-repo references in a local issue tracker?

The best way to organize cross-repo references in a local issue tracker is by using YAML link graphs and frontmatter. The local-issues CLI enforces strict input validation while managing these links across repositories.

Do I need the local-issues CLI to create and close issues in the .issues directory?

Yes, the local-issues CLI is required to create and close issues in the .issues directory. The CLI handles all operations including create, close, comment, link, and list functions with strict input validation.