refresh-issue

Refresh a Linear issue by verifying code, tests, and documentation status.

Updated Feb 20, 2026

Search Tags:#developer tools #documentation #workflow automation #code sync #issue tracking #linear

Ready to run

npx skills add https://github.com/jamesc/skills --skill refresh-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: refresh-issue
Source: https://github.com/jamesc/skills/tree/main/skills/refresh-issue
Command: npx skills add https://github.com/jamesc/skills --skill refresh-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill ensures that issue trackers accurately reflect the current state of the codebase and documentation, preventing stale or irrelevant tasks.

Core Features & Use Cases

Automated Issue Verification: Checks if an issue is still relevant, already fixed, or obsolete.
Documentation Alignment: Compares issue requirements against the latest documentation.
Code State Analysis: Examines relevant code files to determine implementation status.
Use Case: When a developer is about to start working on a ticket, they can use this skill to quickly confirm that the ticket's description and acceptance criteria are up-to-date with the latest code and documentation, saving time and preventing rework.

Quick Start

Use the refresh-issue skill to sync issue BT-123 with the latest code and documentation.

Frequently Asked Questions about refresh-issue

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

FAQPage Schema

How do I sync Linear issues with my codebase and documentation?▼

To sync Linear issues with code and documentation, you can use an automated workflow that examines current code, tests, and docs to verify implementation status. It aligns issue descriptions and acceptance criteria, then updates the issue with a structured review summary.

How do I check if a Linear issue is already fixed or obsolete before starting work?▼

Checking if a Linear issue is fixed or obsolete involves examining relevant code files and documentation to determine implementation status. An automated verification process compares issue requirements against the latest codebase state to confirm relevance.

What is the best way to align issue tracker descriptions with current code state?▼

Aligning issue tracker descriptions with code state requires analyzing code files, tests, and documentation to determine current implementation status. Automated issue verification compares requirements against the latest documentation and updates the tracker with a structured review summary.

Does Linear issue tracking support automated verification of acceptance criteria?▼

Linear issue tracking supports automated verification of acceptance criteria by examining code, tests, and documentation. This workflow determines if an issue is fixed, partially fixed, obsolete, or blocked, then updates issue status and comments with a structured review summary.

When do I need to refresh issue tracker data against the latest codebase?▼

You need to refresh issue tracker data against the latest codebase when preparing to start work on a ticket. This ensures the ticket's description, acceptance criteria, and file references accurately reflect current code and documentation, preventing stale tasks and rework.

Why are my Linear issue descriptions out of sync with my current code?▼

Linear issue descriptions fall out of sync with current code when the codebase and documentation evolve without updating the tracker. Automated issue verification examines code files and tests to detect this drift, then aligns descriptions and acceptance criteria with the actual implementation status.