Parse work logs and generate weekly Jira reports in Markdown.
npx skills add https://github.com/dEitY719/dotfiles --skill make-jira
Please help me install this Agent Skill. Skill: make-jira Source: https://github.com/dEitY719/dotfiles/tree/main/claude/skills/make-jira Command: npx skills add https://github.com/dEitY719/dotfiles --skill make-jira
Manual aggregation of weekly work entries into Jira reports is time-consuming and error-prone, especially when trying to reconcile hours across multiple Jira keys.
Run /make-jira to generate the current week's Jira report from your work_log.txt.
High-intent search queries and answers about installing and using this skill.
To generate a weekly Jira report from a work log, you need a work_log.txt file in your user home directory. The tool parses this file, groups entries by Jira keys, aggregates hours, and outputs a Markdown report for the current ISO week.
Yes, you can optionally include git commit details in your weekly Jira work log report. The tool fetches commit context to provide richer summaries alongside the aggregated hours grouped by Jira keys.
You need a plain text file named work_log.txt located in your user home directory to automate Jira reporting. The tool reads this specific file to parse work entries and aggregate hours per Jira key.
Generated weekly Jira Markdown reports are saved to the rca-knowledge/docs/jira-records/ directory. The output file is named using the current ISO week format, such as YYYY-W##-report.md.
The best way to aggregate hours across multiple Jira keys is to automate the grouping process with a parsing tool. It reads your work logs, sums the hours per Jira key, and generates a clean Markdown report.
Manual aggregation of weekly work entries into Jira reports fails because it is time-consuming and error-prone, especially when reconciling hours across multiple Jira keys. Automating the parse and group process eliminates these errors.
mayurpiseCreate Epic, Stories, and Sub-tasks in Jira from a jira-export.md file via MCP-Jira.
KIM-KYOUNG-OHAnalyze weekly Claude Code session logs and generate markdown usage reports.
Hamad-CenterRecord git commit SHA and branch with ticket info in `.drift/config.json`.
diShine-digital-agencyAggregate weekly work logs from sessions and Asana into client- and phase-based summaries with Markdown and CSV outputs.
