skills.rest
marcuskrogh
marcuskroghCOMMUNITY
Explore all skills by this author →
GitHub

tracker

Standardize issue lifecycle operations across GitHub, Jira, Linear, and Markdown backends.

1|Updated Jul 1, 2026
Search Tags:#github#linear#jira#workflow-automation#issue-tracking#project-management
One-click install
npx skills add https://github.com/marcuskrogh/skills --skill tracker-marcuskrogh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tracker
Source: https://github.com/marcuskrogh/skills/tree/main/skills/tracker
Command: npx skills add https://github.com/marcuskrogh/skills --skill tracker-marcuskrogh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the fragmentation of project management by providing a unified interface for issue tracking that works regardless of whether your team uses GitHub, Jira, Linear, or local Markdown files.

Core Features & Use Cases

  • Cross-Platform Abstraction: Standardizes issue operations like fetching, creating, and transitioning across disparate backends.
  • Markdown Mirroring: Maintains a local, human-readable record of project status even when using remote issue trackers.
  • Workflow Integration: Enables seamless handoffs between pipeline skills by using a consistent issue-key contract.

Quick Start

Ask the agent to initialize the project tracker by running the setup command to configure your preferred backend provider.

Frequently Asked Questions about tracker

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

FAQPage Schema
How do I manage issue tracking across GitHub, Jira, and Linear from a single interface?▼

Unified issue tracking standardizes issue management operations across GitHub, Jira, Linear, and local Markdown backends. It provides a consistent contract for issue creation, status transitions, and cross-referencing within agent-driven development pipelines.

Can I keep a local Markdown record of issues when using remote trackers like Jira?▼

Yes, Markdown mirroring maintains a local, human-readable record of project status even when using remote issue trackers. This ensures a consistent local backup while facilitating cross-platform artifact linking.

What is the best way to standardize project status transitions in automated workflows?▼

Standardizing project status transitions requires a unified issue-key contract that enables seamless handoffs between pipeline skills. This approach facilitates consistent issue lifecycle management across disparate tracking backends.

Does unified issue tracking work with local Markdown files as a backend provider?▼

Yes, local Markdown files function as a supported backend provider for issue tracking. The system implements a unified contract for issue lifecycle management, enabling creation and updates without requiring a remote platform.

How do I initialize cross-platform project tracking for agent-driven development?▼

To initialize cross-platform project tracking, ask the agent to run the setup command and configure your preferred backend provider. This configures the unified interface for subsequent issue management operations.

Related Skills

Explore More Software Engineering Skills→
e601201e601201

setup-matt-pocock-skills

Configure issue tracking, triage labels, and domain docs for GitHub, GitLab, or local markdown.

Community
Advanced
Chanw-researchChanw-research
38

exp-status

Monitor running experiments across local and remote environments and generate status reports.

Official
Advanced
jfriisjjfriisj

obsidian-workflow

Coordinate multi-agent workflows by building relational memory graphs in Obsidian via MCP tools.

Community
Advanced
faw01faw01
18

expo-ui

Create cross-platform mobile UI trees with SwiftUI and Jetpack Compose overrides.

Community
Advanced