jinn-sync

Audit Linear In Progress issues and update statuses via MCP tools.

1|Updated Sep 2, 2019
One-click install
npx skills add https://github.com/hackefeller/hominem --skill jinn-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jinn-sync
Source: https://github.com/hackefeller/hominem/tree/main/.claude/skills/jinn-sync
Command: npx skills add https://github.com/hackefeller/hominem --skill jinn-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconcile Linear MCP state with the actual progress reflected in the codebase.

Core Features & Use Cases

  • Audit In Progress issues to ensure they reflect completed work
  • Identify stale issues and undocumented work, restoring order on the Linear board
  • Generate a clear sync report and apply necessary updates to issue statuses

Quick Start

Issue a jinn-sync run to reconcile your Linear board with the current codebase.

Frequently Asked Questions about jinn-sync

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

FAQPage Schema
How do I reconcile Linear issues with my codebase?

To reconcile Linear issues with your codebase, you can run an audit process that compares In Progress issues against actual progress. It identifies stale items, back-fills undocumented work, generates a sync report, and applies status updates to preserve board integrity.

What is the best way to audit stale Linear issues?

The best way to audit stale Linear issues is to run a reconciliation process against your codebase. It identifies stale items, back-fills undocumented work, and applies necessary updates to issue statuses to restore order on the Linear board.

How does syncing Linear with a codebase work?

Syncing Linear with a codebase works by collecting issue data via MCP, reading issue details, and comparing them against actual codebase progress. It then generates a sync report and applies status or comment updates to reconcile the board.

Does the Linear MCP integration support back-filling undocumented work?

Yes, the Linear MCP integration supports back-filling undocumented work by collecting and reading issue details, then applying updates via MCP functions. It reconciles the Linear state with actual codebase progress to identify gaps and restore board order.

Why are my In Progress Linear issues not reflecting completed work?

Your In Progress Linear issues may not reflect completed work because the board state has drifted from actual codebase progress. Running a reconciliation sync audits these issues, identifies stale items, and updates their statuses to match reality.