dev-timesheet-reportlisted

# Dev Timesheet Report Reconstruct what a developer actually worked on over a date range from the traces the work left behind, and render it as a timesheet. The evidence is scattered across systems that each know only part of the story: local commits know *what changed* but not *why*, the board knows the ticket and its title but not the hours at the keyboard, the code host knows about review work that produces no commit at all, and the wiki holds the days that produced a document instead of a diff. This skill gathers all of them, matches them to ids, labels each piece of activity, and collapses it into one line per day per item per activity. `<SKILL_DIR>` below is this skill's own announced base directory (the path shown when this skill loads, ending in `.../skills/dev-timesheet-report`). Scripts are at `<SKILL_DIR>/scripts/`, references at `<SKILL_DIR>/references/`. **Config lives at `~/.dev-timesheet-report/config.json`** — the user's home directory, not this repo, matching how `estimator` and `naturalize` store personal setup. It is written once and reused every run. This skill is **read-only against every source**. It never writes a worklog, comment or any other record back to Jira or a code host. ## Prerequisites **Hard requirements** — without these the skill cannot run at all: - **Python 3 or Node ≥ 18** for the bundled scripts. Either is fine; they are twins. If neither exists, say so and stop (Step 5). - **`git` on `PATH`**, for local repository scanning.