sv-issue-tracking

Manage work items and synchronize task status with Git code changes.

1|1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/mbtz/agent-skills --skill sv-issue-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sv-issue-tracking
Source: https://github.com/mbtz/agent-skills/tree/main/skills/sv-task-issue-tracking
Command: npx skills add https://github.com/mbtz/agent-skills --skill sv-issue-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines work item management by providing a command-line interface for tracking tasks and ensuring their synchronization with code changes.

Core Features & Use Cases

  • Task Management: Create, list, show, update, and close work items.
  • Status Synchronization: Keeps task status aligned with code commits.
  • Use Case: A developer can quickly create a new task for a bug fix, mark it as in progress, and then close it once the fix is committed, all from their terminal.

Quick Start

Use sv task to list all open work items.

Frequently Asked Questions about sv-issue-tracking

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

FAQPage Schema
How do I track task status with code changes in Git?

You can track task status with Git by using a command-line tool that synchronizes work items directly with code commits. Tasks are stored in a local `.tasks/tasks.jsonl` file, ensuring your work item state stays aligned with your repository history.

What is the best way to manage issue tracking from the command line?

Command-line issue tracking can be managed by creating, listing, and updating work items directly in your terminal. This approach stores tasks locally in a JSONL file and integrates with your version control system to sync status updates with commits.

How do I create and close a bug fix task without leaving the terminal?

To create and close a task from the terminal, use the `sv task` command-line interface to generate a new work item, update its status to in progress, and close it once your fix is committed. All task data is persisted in `.tasks/tasks.jsonl`.

Does this issue tracking workflow require an external database?

No external database is required for this issue tracking workflow. Tasks are stored locally in a `.tasks/tasks.jsonl` file within your project, allowing you to manage work items and synchronize them with Git changes entirely offline.

Can I list all open work items using the sv task CLI?

Yes, you can list all open work items by running the `sv task` command in your terminal. This CLI tool reads from the local `.tasks/tasks.jsonl` file to display current tasks and their synchronization status with your codebase.