Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
Enable, disable, or configure TimeClock integration for the current project
How this command is triggered — by the user, by Claude, or both
Slash command
/timeclock-integration:configure [enable|disable|status]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# TimeClock Integration Configuration You are configuring TimeClock automatic time tracking for the current project. ## Configuration File The settings live in `.claude/timeclock-integration.local.md` in the project root. This file controls whether TimeClock integration is active for this project. ## Actions Based on the user's argument: ### `enable` (or no argument) 1. Ask the user for the project name to use in TimeClock (suggest the current directory name as default). 2. Ask for the TimeClock API URL (default: `http://localhost:7843`). 3. Create or update `.claude/timeclock-integra...
You are configuring TimeClock automatic time tracking for the current project.
The settings live in .claude/timeclock-integration.local.md in the project root. This file controls whether TimeClock integration is active for this project.
Based on the user's argument:
enable (or no argument)http://localhost:7843)..claude/timeclock-integration.local.md with:---
enabled: true
project_name: "<user's answer>"
api_url: "<user's answer>"
---
# TimeClock Integration
This project has automatic TimeClock time tracking enabled.
When Claude Code sessions start in this project, TimeClock will automatically:
- Clock in to the matching task
- Create tasks from approved plans
- Switch tasks as work context changes
disableenabled: true to enabled: false.statusnpx claudepluginhub columbiafit/timeclock-marketplace --plugin timeclock-integration/hammertimeCreates behavioral guardrail rules that run as a Stop hook to catch and correct model behaviors. Supports timer rules with duration prefix, behavior-based rules from descriptions, and a full status dashboard when called with no arguments.
/time-entryLogs time worked against Autotask tickets or projects, handling billability, budget limits, and approval. Returns time entry ID, billing amount, and status.
/os-hooksManages Claude Code Hooks configuration — installs, removes, and shows status of hook events that sync CC operations to an AI Team OS Dashboard. Supports install and remove subcommands.
/auto-captureToggles automatic activity capture on or off for the current project, or checks its status. Also supports viewing captured activities via /nemp-pro:activity.
/serveBidirectionally sync task details between Claude Code and external task managers (Jira, Linear, Asana, ClickUp, GitHub) via MCP — pull task info from a URL or push status updates/comments after work.
/configureInteractively enable or disable hookify rules by selecting from a list of existing rules. Reads rule files, toggles the enabled field, and applies changes immediately.