check-todos

Check GitHub PR review comments, self-announced follow-ups, and linked Jira issue status.

2|Updated Jun 1, 2015
One-click install
npx skills add https://github.com/TimoFreiberg/dotfiles --skill check-todos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-todos
Source: https://github.com/TimoFreiberg/dotfiles/tree/main/agents/skills/check-todos
Command: npx skills add https://github.com/TimoFreiberg/dotfiles --skill check-todos

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill proactively identifies and surfaces any outstanding tasks or commitments related to your current work, ensuring nothing falls through the cracks.

Core Features & Use Cases

  • Review Unresolved Comments: Automatically checks for open review threads on GitHub Pull Requests.
  • Track Commitments: Identifies self-announced follow-ups within PR comments.
  • Jira Integration: Links to and reports the status of associated Jira issues.
  • Use Case: Before starting your day, run this skill to get a clear picture of all pending action items from code reviews, your own commitments, and linked Jira tickets, allowing you to prioritize effectively.

Quick Start

Check for any open obligations related to the current task.

Frequently Asked Questions about check-todos

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

FAQPage Schema
How do I check for unresolved PR review comments and outstanding task obligations?

To check for unresolved PR review comments and outstanding obligations, use this Skill to automatically scan GitHub Pull Requests. It identifies open review threads, self-announced follow-ups, and linked Jira issue statuses.

What is the best way to track self-announced follow-ups in GitHub PRs?

Tracking self-announced follow-ups in GitHub PRs is done by analyzing your PR comments for commitments. This Skill detects these obligations and surfaces them alongside your unresolved code review feedback and Jira ticket statuses.

Do I need Jira API credentials to check linked Jira issue status?

You need Jira API credentials to check linked Jira issue status. While GitHub CLI and cURL are required for core PR review checks, Jira credentials are optional but necessary for comprehensive analysis of associated Jira tickets.

Can I use GitHub CLI to manage code review feedback and task tracking?

You can use GitHub CLI to manage code review feedback by running this Skill. It leverages GitHub CLI and cURL to automatically check for open obligations, including unresolved PR review threads and your own follow-up commitments.

Why does tracking outstanding obligations across GitHub and Jira fail without cURL?

Tracking outstanding obligations across GitHub and Jira requires cURL to execute the necessary API requests. This Skill depends on both GitHub CLI and cURL to fetch unresolved PR comments, follow-ups, and Jira issue statuses.