jira-task-manager

What This Skill Does

The jira-task-manager is a robust automation suite designed for OpenClaw agents to interface seamlessly with JiraATX. This skill streamlines project management for the DS project by enabling agents to handle the full lifecycle of a task—from discovery and assignment to technical implementation and testing. It integrates directly with internal documentation via references/jira.md and repository mappings in references/repos.json to ensure that the AI remains context-aware of both the business requirements in Jira and the codebase structure.

Installation

You can install this skill directly via the OpenClaw hub using the following command: clawhub install openclaw/skills/skills/clairproqc-star/jira-task-manager

Ensure that you have provided the necessary API credentials in the references/jira.md file, as the skill requires valid authentication tokens to communicate with your Jira instance securely. Once installed, the agent will automatically detect and execute workflows based on task triggers.

Use Cases

• Project Triage: Quickly list all 'To Do' tasks assigned to specific team members to prioritize daily workflows.
• Technical Implementation: Automatically sync local repositories to the correct branch associated with a specific Jira issue, read relevant source files, and run tests end-to-end.
• Issue Reporting: Create, comment, and transition tickets dynamically based on completion of automated tasks or manual user feedback.
• State Management Debugging: Special troubleshooting capabilities for React/Zustand applications, helping developers audit and fix stale closure or re-rendering issues by ensuring global state persistence.

Example Prompts

1. "List all my To Do tasks in project DS for today."
2. "Work on DS-402, please check the requirements and set up the repo."
3. "Can you add a comment to DS-402 saying that the unit tests passed and the feature is ready for QA?"

Tips & Limitations

• Safety First: When using the 'Full Task Execution Flow', the agent will stop and wait for your manual approval before performing irreversible actions like merging code or updating ticket statuses. Always review the report provided by the agent after test execution.
• Dependencies: Ensure your references/repos.json is updated regularly so the agent can correctly identify where the source code for specific issue keys is located.
• State Persistence: When debugging frontend issues, use the provided guidance on selector-based Zustand subscriptions to avoid broadening the cache scope unnecessarily.