dustinestes
- 12 skills
- 0 followers
- 6 hours ago last updated
- ▌ Clockify Init · dustinestesBootstrap Clockify for a repo: AskQuestion for workspace only, write v4 .clockify/config.yml from the plugin example (plugin / scope / entry), and default-ignore personal time-tracking files. Use when setting up time tracking (timer or enter-time). Safe to re-run: does not overwrite existing config unless the user asks. Does not enable agent automation — that is clockify-automate.
- ▌ Clockify Status · dustinestesReport whether a Clockify timer is running and its metadata (description, project, task, start, duration, runaway ceiling). Use when the user asks if they are tracking, what is running, or timer status. Read-only.
- ▌ Clockify Uninit · dustinestesRemove Clockify integration artifacts from a consumer repo: .clockify/, clockify rule, Clockify-owned hooks, and the managed gitignore stanza. Use when uninstalling repo Clockify standards. To pause and keep settings, use clockify-automate-disable; to reset automate yaml and keep config, use clockify-unautomate. Does not uninstall the Clockify Agent Plugin unless the user asks.
- ▌ Clockify Automate · dustinestes bundleTurn on agent-mediated Clockify tracking: if .clockify/config.yml is missing, run minimal clockify-init first, then forge wizard (GitHub) + Cursor Plan/Debug platforms + runaway wizard, ensure project/tasks, write Cursor rules, and when runaway is enabled install Clockify-owned runaway hooks. Use when the user wants the agent to start/stop timers in the issue/PR workflow and Plan/Debug modes. Safe to re-run.
- ▌ Clockify Summarize · dustinestesSummarize Clockify time for today or a date range (totals by project, entry count). Use when the user asks how much they tracked, a timesheet snapshot, or today's Clockify summary. Does not start or stop timers.
- ▌ Clockify Enter Time · dustinestesCreate a completed Clockify time entry with an explicit start and end (Clockify Manual). Use when the user logs a range, backfills forgotten time, or does not want a running timer. Does not round. Infers a window only when times are omitted, and always confirms before writing.
- ▌ Clockify Stop Timer · dustinestesStop the currently running Clockify timer. Use when the user asks to stop tracking, clock out, or finish an issue/PR in this session. Honors timer rounding and overlap. Does not summarize the whole day.
- ▌ Clockify Unautomate · dustinestesFull rollback of agent-mediated Clockify tracking: remove the clockify Cursor rule and Clockify-owned hooks, and reset entry.automated in .clockify/config.yml to init/example defaults (all forge.*.enabled false, empty triggers, platforms.cursor off, modes cleared). Does not change plugin, scope, timer, or manual. Use when the user wants to undo automate — not a temporary pause (use clockify-automate-disable / clockify-automate-enable for that).
- ▌ Clockify Start Timer · dustinestesStart a Clockify running timer for the current repo. Use when the user asks to start tracking, clock in, or start a timer on an issue. Honors the timer block in .clockify/config.yml. Warns before stopping a different running timer. Optional backdated start.
- ▌ Publish Release · dustinestesCut a GitHub Release that publishes @dustinestes/clockify-agent-plugin to npm. Bumps package.json, plugin.json, and .cursor-plugin/plugin.json to the same version, then creates tag vX.Y.Z. Use when the user asks to publish a new version, cut a release, ship to npm, or create a GitHub Release for this package. Do not bump or tag unless they asked to publish.
- ▌ Clockify Automate Enable · dustinestesResume agent-mediated Clockify tracking after clockify-automate-disable: set entry.automated.enabled true, restore platforms.cursor.enabled from preserved modes, rewrite .cursor/rules/clockify.mdc, and reinstall runaway hooks when settings.runaway.enabled is still true. Skips forge/Cursor/runaway wizards unless settings are missing — then redirect to clockify-automate. Use when the user wants to turn automation back on without a full re-wizard.
- ▌ Clockify Automate Disable · dustinestesTemporarily pause agent-mediated Clockify tracking without wiping settings: remove the clockify Cursor rule and Clockify-owned runaway hooks, set entry.automated.enabled false and platforms.cursor.enabled false, but keep forge, settings.on_start, triggers, settings.runaway prefs, and modes. Distinct from clockify-unautomate (full rollback). Use when the user wants a pause they can resume with clockify-automate-enable.