work-receipt

What This Skill Does

The work-receipt skill is an essential auditing tool for developers, acting as a personal assistant that monitors your coding progress throughout an active session. Instead of relying on vague memory or chaotic commit logs when a manager asks for a status update, this tool synthesizes your git history, file modifications, test outcomes, and terminal interaction into a clean, structured summary. It acts as a professional record-keeper, transforming raw technical changes into human-readable highlights. By summarizing accomplishments, decisions made, architectural trade-offs, and lingering technical debt, it ensures you can clearly articulate your value. Whether you are conducting a daily standup, performing a project handoff, or simply reviewing your own professional growth, this skill provides the definitive proof of your work, ensuring no effort goes unrecorded.

Installation

You can add this skill to your OpenClaw environment by running the following command in your terminal:

clawhub install openclaw/skills/skills/jcools1977/work-receipt

Ensure that your OpenClaw agent has the necessary permissions to access your git repository and file system so it can accurately analyze your session data.

Use Cases

• Daily Standups: Quickly generate a bulleted list of what you accomplished during the day to share with your team via Slack or during live meetings.
• Project Handoffs: Provide an automated summary of technical decisions and pending TODOs for the next developer inheriting your branch.
• Self-Review: Analyze your own productivity patterns to identify where you spend the most time, helping you improve your development workflow.
• Documenting Technical Debt: Explicitly catalog shortcuts taken under time pressure so they aren't forgotten, creating a backlog for future refinement sprints.

Example Prompts

1. "I'm done for the day. Can you generate a work receipt summarizing everything I've pushed to the feature/login-refactor branch?"
2. "Please run a work receipt for this session. Make sure to highlight the architectural changes I made to the database schema and list any lingering TODOs in the controller files."
3. "I need to send an update to my lead. Create a concise summary of my session that focuses on the bug fixes I implemented and the specific test suites I updated."

Tips & Limitations

• Be Descriptive: The more context you provide in your commit messages, the better the work receipt will be at explaining the 'why' behind your changes.
• Session Scope: This tool works best when you trigger it immediately after concluding a focused block of work. If you leave the session open too long, the 'time spent' metric may become less precise.
• Privacy: Remember that the work receipt reads your file changes; ensure you have appropriate .gitignore files set up so the agent does not ingest sensitive environment variables or local-only secret keys. The tool is designed for reporting, not auditing production secrets.