Profile My skills Saved My plugins Edit profile Submit a skill

← all publishers

qili09

@qili09 source repo

3 published skills

  1. ▌
    Time Report · qili09 bundle
    Log the time spent on a Jira story during the current Claude Code session as a Jira worklog (mirrored into Tempo Timesheets), computed from the session transcript instead of typed by hand. Use when the user says "log time", "log my time", "time report", "record this in Tempo", "how long did I spend on <KEY>", or when a Stop-hook nudge reports unlogged time — and at the natural end of any session in which a Jira story (e.g. PROJ-12345) was actively worked on, offer to run it. Do NOT use it for editing or reporting on Tempo timesheets in general, for estimating future effort, or for stories that were merely mentioned in passing.
    0 installs
  2. ▌
    Autonomous Reply · qili09 bundle
    Autonomously answer an inbound message on any communication channel — reply to a Gmail thread, respond to a Slack or Google Chat message, or assess a Jira issue and draft the comment — grounding the response in supplied context sources (Google Drive docs, local files, GitHub repos, other tickets). Use this whenever there is an inbound message to answer and the user points at it — "reply to this email", "respond to Richard's Slack message", "assess this Jira story and add my comment", "draft a response to X, here's the background doc" — even if they never name the skill. The skill auto-selects tone, format, and delivery route per channel so the user never has to re-explain them. Also use it when the follow-up to a thread or meeting notes is a new tracker issue — "create a ticket from these notes and link it to ABC-123" — since the issue is grounded in the same sources the same way. Do NOT use it for composing brand-new outbound messages with no inbound message to answer (ordinary drafting), and do NOT use it w
    0 installs
  3. ▌
    Architecture Decision Review · qili09 bundle
    Run a rigorous, evidence-first review of an architecture or platform decision, land it as an ADR, and translate it into tracker stories. Use this whenever the user weighs two or more technical options and asks for advice, a recommendation, a comparison, or a justification — "should we use X or Y", "which project/platform should host this", "is it worth migrating", "help me justify this decision", "how much would we save" — even if they never say "ADR" or "architecture decision". Also use it when the user asks to draft or update an ADR, to create Jira/tracker stories from a design decision, or presents a decision already half-made and wants it validated. The heart of the skill is verifying the user's stated premises against primary sources before recommending, so trigger it even when the user sounds certain of the answer. Do NOT use it for generic technology overviews or casual comparisons with no project context to verify and no durable decision to record. Optionally takes any number of source arguments (GitH
    0 installs