@knpkv/jira-clockify 0.5.0 → 1.0.1

package/nvim/lua/jcf/init.lua

@@ -23,25 +23,25 @@ function M.setup(opts)
       key = require("jcf.branch").detect()
     end
     if key then
-      vim.fn.jobstart({ M.config.binary, "start", key }, { detach = true })
+      vim.fn.jobstart({ M.config.binary, "timer", "start", key }, { detach = true })
       vim.notify("jcf: starting timer on " .. key, vim.log.levels.INFO)
     else
-      -- No key and no branch match → open jcf start in float (has built-in fuzzy selector)
-      require("jcf.float").run_command(M.config, "start")
+      -- No key and no branch match: open jcf timer start in float.
+      require("jcf.float").run_command(M.config, "timer", "start")
     end
   end, { nargs = "?", desc = "Start jcf timer" })
 
   vim.api.nvim_create_user_command("JcfStop", function()
     -- Open in float so the comment prompt is interactive
-    require("jcf.float").run_command(M.config, "stop")
+    require("jcf.float").run_command(M.config, "timer", "stop")
   end, { desc = "Stop jcf timer" })
 
   vim.api.nvim_create_user_command("JcfDiscard", function()
-    require("jcf.float").run_command(M.config, "discard")
+    require("jcf.float").run_command(M.config, "timer", "discard")
   end, { desc = "Discard jcf timer (delete Clockify entry)" })
 
   vim.api.nvim_create_user_command("JcfLog", function(args)
-    local cmd_args = { "log" }
+    local cmd_args = { "timer", "log" }
     if args.args ~= "" then
       for word in args.args:gmatch("%S+") do
         table.insert(cmd_args, word)
@@ -51,11 +51,11 @@ function M.setup(opts)
   end, { nargs = "*", desc = "Log past work manually" })
 
   vim.api.nvim_create_user_command("JcfEdit", function()
-    require("jcf.float").run_command(M.config, "edit")
+    require("jcf.float").run_command(M.config, "timer", "edit")
   end, { desc = "Edit running timer" })
 
   vim.api.nvim_create_user_command("JcfStatus", function()
-    require("jcf.float").run_command(M.config, "status")
+    require("jcf.float").run_command(M.config, "timer", "status")
   end, { desc = "Show timer status" })
 
   -- Start polling for external timer changes

package/nvim/lua/jcf/state.lua

@@ -26,7 +26,7 @@ function M.read(state_path)
   return cached
 end
 
--- Periodically run `jcf status` to sync state file with Clockify
+-- Periodically run `jcf timer status` to sync state file with Clockify
 -- This detects externally stopped timers
 function M.start_poll(config, interval_ms)
   if poll_timer then
@@ -36,8 +36,8 @@ function M.start_poll(config, interval_ms)
 
   poll_timer = uv.new_timer()
   poll_timer:start(interval_ms, interval_ms, vim.schedule_wrap(function()
-    -- jcf status updates ~/.jcf/state.json and detects external stops
-    vim.fn.jobstart({ config.binary or "jcf", "status" }, {
+    -- jcf timer status updates ~/.jcf/state.json and detects external stops
+    vim.fn.jobstart({ config.binary or "jcf", "timer", "status" }, {
       on_stdout = function() end,
       on_stderr = function() end,
       detach = true,

package/nvim/lua/jcf/telescope.lua

@@ -12,8 +12,8 @@ function M.pick(config)
   local actions = require("telescope.actions")
   local action_state = require("telescope.actions.state")
 
-  -- Get tickets via jcf list --json
-  local result = vim.fn.system({ config.binary, "list", "--json" })
+  -- Get tickets via jcf issue list --json
+  local result = vim.fn.system({ config.binary, "issue", "list", "--json" })
   local tickets_ok, tickets = pcall(vim.json.decode, result)
   if not tickets_ok or not tickets then
     vim.notify("jcf: failed to get tickets", vim.log.levels.ERROR)
@@ -38,7 +38,7 @@ function M.pick(config)
         actions.close(prompt_bufnr)
         local selection = action_state.get_selected_entry()
         if selection and selection.value and selection.value.key then
-          vim.fn.jobstart({ config.binary, "start", selection.value.key }, { detach = true })
+          vim.fn.jobstart({ config.binary, "timer", "start", selection.value.key }, { detach = true })
           vim.notify("jcf: starting timer on " .. selection.value.key, vim.log.levels.INFO)
         end
       end)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@knpkv/jira-clockify",
-  "version": "0.5.0",
+  "version": "1.0.1",
   "description": "TUI for Jira-Clockify time tracking, attachable to neovim",
   "license": "MIT",
   "author": "knpkv",
@@ -23,11 +23,11 @@
     "@opentui/react": "https://pkg.pr.new/anomalyco/opentui/@opentui/react@367a94087821b3b5feedd35bbb57df43b10a286e",
     "effect": "4.0.0-beta.87",
     "react": "^19.2.7",
-    "@knpkv/agent-skills": "^0.2.0",
-    "@knpkv/atlassian-common": "^0.3.0",
+    "@knpkv/agent-skills": "^0.2.2",
+    "@knpkv/atlassian-common": "^0.4.0",
+    "@knpkv/clockify-api-client": "^0.3.0",
     "@knpkv/jira-api-client": "^0.3.0",
-    "@knpkv/jira-cli": "^0.3.0",
-    "@knpkv/clockify-api-client": "^0.3.0"
+    "@knpkv/jira-cli": "^1.1.0"
   },
   "devDependencies": {
     "@effect/vitest": "4.0.0-beta.87",

package/skills/jcf/SKILL.md

@@ -11,8 +11,9 @@ Use the `jcf` binary to manage Jira-backed Clockify timers.
 
 - Configure both services before timer operations: Jira OAuth and Clockify API key.
 - Use `jcf auth status` to check readiness.
+- `jcf` uses the shared Jira CLI auth profile store; for multi-site Jira accounts, use `jira auth profiles` and `jira auth use <profile>` before timer operations when the `jira` binary is available. When the `atlassian` binary is available, prefer `atlassian profiles doctor` to confirm that Jira Clockify is using the intended `jira-cli` auth store and `atlassian auth refresh` for expired Jira tokens.
 - Timer operations write to Clockify and may write Jira worklogs; confirm ambiguous ticket keys, durations, dates, and comments before running them.
-- Use `jcf list --json` when an agent needs structured ticket data.
+- Use `jcf issue list --json` when an agent needs structured ticket data.
 
 ## Setup
 
@@ -22,6 +23,9 @@ jcf auth jira create
 jcf auth jira configure
 jcf auth jira login
 jcf auth clockify setup
+
+atlassian profiles doctor
+atlassian auth refresh
 ```
 
 Configure defaults:
@@ -46,44 +50,45 @@ jcf tui
 List available Jira tickets:
 
 ```bash
-jcf list
-jcf list --json
+jcf issue list
+jcf issue list --json
 ```
 
 Start work:
 
 ```bash
-jcf start PROJ-123
-jcf start PROJ-123 --ago 15m
-jcf start PROJ-123 --since 09:30
-jcf start PROJ-123 --project <clockify-project-id> --billable
+jcf timer start PROJ-123
+jcf timer start PROJ-123 --ago 15m
+jcf timer start PROJ-123 --since 09:30
+jcf timer start PROJ-123 --project <clockify-project-id> --billable
 ```
 
 Stop or discard current work:
 
 ```bash
-jcf status
-jcf stop
-jcf stop --project <clockify-project-id> --billable
-jcf discard
+jcf timer status
+jcf timer stop
+jcf timer stop --project <clockify-project-id> --billable
+jcf timer discard
 ```
 
 Log completed work manually:
 
 ```bash
-jcf log PROJ-123 --time 1h30m
-jcf log PROJ-123 --time 45m --date 2026-06-24 --at 09:00 --comment "Pairing on release notes"
+jcf timer log PROJ-123 --time 1h30m
+jcf timer log PROJ-123 --time 45m --date 2026-06-24 --at 09:00 --comment "Pairing on release notes"
 ```
 
 Edit the running timer:
 
 ```bash
-jcf edit
+jcf timer edit
 ```
 
 ## Agent Workflow
 
-1. Run `jcf auth status` and `jcf status` before changing timer state.
-2. Use `jcf list --json` to resolve issue keys when the user gives a vague ticket description.
-3. Prefer explicit flags for non-interactive work: issue key, duration, date, time, project id, billable flag, and comment.
-4. If no timer is running, `jcf stop` may offer an interactive correction interval; use `jcf log` for deterministic manual logging.
+1. Run `jcf auth status` and `jcf timer status` before changing timer state.
+2. Use `jcf issue list --json` to resolve issue keys when the user gives a vague ticket description.
+3. Verify the active Jira profile when the user names a Jira site/account or before posting worklogs; `atlassian profiles doctor` shows Jira Clockify as a consumer of the `jira-cli` auth store.
+4. Prefer explicit flags for non-interactive work: issue key, duration, date, time, project id, billable flag, and comment.
+5. If no timer is running, `jcf timer stop` may offer an interactive correction interval; use `jcf timer log` for deterministic manual logging.

package/skills/jcf/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Jira Clockify CLI"
   short_description: "Track Jira work in Clockify"
-  default_prompt: "Use $jcf to start, stop, log, or inspect Jira Clockify timers."
+  default_prompt: "Use $jcf to run timer, issue, and sync commands for Jira-backed Clockify time tracking."