qualia-report

Generate dated markdown session reports from git logs and tracking data.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Qualiasolutions/qualia-framework --skill qualia-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qualia-report
Source: https://github.com/Qualiasolutions/qualia-framework/tree/main/skills/qualia-report
Command: npx skills add https://github.com/Qualiasolutions/qualia-framework --skill qualia-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-of-day session reporting workflow so employees no longer manually compile commits, project state, and notes before clocking out. It ensures a consistent, auditable report file is created, committed, and optionally uploaded to the ERP to satisfy timekeeping and handoff requirements.

Core Features & Use Cases

  • Gather Recent Activity: Collects recent git commits, branch, project directory, and state information from state.js and tracking.json.
  • Synthesize Concise Reports: Produces a dated markdown session report with What Was Done, Blockers, Next Steps, and a commits list.
  • Commit, Push, and Upload: Writes .planning/reports/report-{date}.md, commits and pushes it to the repo, and optionally POSTs a structured JSON payload to the configured ERP endpoint.
  • State Update: Transitions local state to activity using state.js to reflect that the session report was generated.
  • Use Case: Daily developer or consultant workflow to standardize end-of-day reports and streamline ERP time/attendance submissions.

Quick Start

Run /qualia-report to generate a concise session report, commit it to the repository, and upload it to the configured ERP if enabled.

Frequently Asked Questions about qualia-report

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

FAQPage Schema
How do I automate end-of-day session reports from recent git commits?

Automating end-of-day session reports involves collecting recent git commits, branch metadata, and project state to generate a dated markdown summary. The report is then committed, pushed to the repository, and optionally submitted to an ERP endpoint for timekeeping.

What is the best way to submit daily developer activity logs to an ERP system?

Submitting daily developer activity logs to an ERP system requires generating a structured JSON payload from recent commits and tracking data. The workflow posts this payload to a configured ERP endpoint using a local API key to satisfy time and attendance requirements.

How does generating a session report update local project state management?

Generating a session report updates local project state management by transitioning the current state to reflect the completed reporting activity. It reads tracking data via state.js and updates the state file to maintain an auditable log of daily progress.

Can I use git commit logs to create structured markdown reports for project tracking?

Yes, you can use git commit logs to create structured markdown reports for project tracking. The process extracts recent commit history and project phase metadata, synthesizing them into a dated markdown file containing sections for completed work, blockers, and next steps.

Do I need a local API key configured to upload session reports to my ERP endpoint?

Yes, a local API key is required to authenticate and POST structured JSON session reports to your configured ERP endpoint. This key enables the automated upload of daily summaries directly from your local development environment before clock-out.

What limitations exist when automating consultant workflow reports with state.js and tracking.json?

Limitations include reliance on existing tracking.json and state.js files for accurate project metadata extraction. If these files are missing or improperly configured, the synthesized markdown report will lack accurate phase data and task tracking context.