reconcile

Reconcile Git Pull Requests with Jira tickets to fix tracking drift.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/taloncjones/dotfiles --skill reconcile-taloncjones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reconcile
Source: https://github.com/taloncjones/dotfiles/tree/main/claude/skills/reconcile
Command: npx skills add https://github.com/taloncjones/dotfiles --skill reconcile-taloncjones

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of maintaining consistency between your Git Pull Requests (PRs) and Jira tickets, ensuring that the project's status is up-to-date and accurate, especially before sprint boundaries or when prompted for cleanup.

Core Features & Use Cases

  • Automated Reconciliation: Propose and confirm fixes for tracking drifts such as untracked PRs, stale statuses, and sprint hygiene issues.
  • Project-Specific Configurations: Allows per-project configurations for better control and accuracy.
  • Use Case: Before a sprint review, use this Skill to automatically reconcile your PRs and Jira tickets, ensuring everything is in order and ready for the upcoming sprint.

Quick Start

Run the reconcile skill to propose and confirm fixes for tracking drift between your PRs and Jira tickets.

Frequently Asked Questions about reconcile

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

FAQPage Schema
How do I reconcile Git pull requests with Jira tickets automatically?

Automated Git and Jira reconciliation requires API access to both platforms to detect tracking drifts like untracked PRs and stale statuses, proposing targeted fixes to ensure sprint hygiene.

What causes sprint hygiene issues when tracking Git pull requests in Jira?

Sprint hygiene issues stem from tracking drift between Git PRs and Jira tickets, specifically untracked pull requests and stale ticket statuses that fail to reflect current development reality.

Can I configure per-project settings for Git and Jira PR reconciliation?

Project-specific configurations are supported for Git and Jira reconciliation, allowing per-project control and accuracy when proposing fixes for tracking drifts across different repositories.

Do I need GitHub and Jira API access to automate PR tracking reconciliation?

GitHub and Jira API access is required to automate pull request reconciliation, as the process operates within specified projects and configurations to detect and resolve tracking inconsistencies.

When should I reconcile my pull requests and Jira tickets?

Pull request and Jira ticket reconciliation is most effective before sprint boundaries or sprint reviews, ensuring project status is up-to-date, accurate, and ready for upcoming sprint planning.

What is the best way to fix untracked PRs and stale statuses across Git and Jira?

The best way to fix untracked PRs and stale statuses is automated reconciliation that proposes and confirms targeted fixes for tracking drift, ensuring Git PR reality matches Jira ticket status.