Generate a concise weekly status update in team format by pulling data from the current Jira sprint (tickets assigned to me), backlog, and recent activity. Outputs bullet points covering "What I worked on" (completed/in-progress this sprint), "What's next" (To Do in current sprint), and standard blockers/leaves fields. When asked for last week's report, covers completed items from last week. Upcoming items are based on the current sprint's To Do tickets. Triggers: /my-weekly-report, "my weekly update", "my weekly status", "generate my weekly", "write my weekly", "my weekly report"
Look up a URL (Teams message, Jira ticket, GitHub PR/issue, incident.io alert) and create a concise backlog entry with a [ref] link. Triggers: /backlog-add, "add this link to backlog", "backlog from link", "look up and add to backlog"
Update the daily backlog by gathering data from Jira sprint, GitHub PRs, and existing backlog, then collaboratively deciding what to work on today. Handles checked-off items, moves existing tasks to Today, and adds new items with reference links. Commits the backlog folder before making changes. Triggers: /update-backlog, "update my backlog", "plan my backlog", "what should I work on today", "refresh backlog", "backlog update"
Look up, read, create, update, search, and navigate Confluence pages using the confluence CLI. Use as fallback when Atlassian MCP tools are unavailable. Triggers: /confluence, "look up confluence page", "check confluence", "read confluence", "create confluence page", "update confluence page", "search confluence", "find in confluence", "confluence page", any Confluence page URL like https://veeam-vdc.atlassian.net/wiki/...
Manage Jira issues using the jira CLI — lookup, create, edit, transition, assign, comment, link, and search. Triggers: /jira, "look up jira issue", "check jira ticket", "create jira issue", "update jira", "move ticket to", "assign issue", "add comment to", "what's the status of PROJ-123", any mention of a Jira issue key like PROJ-123
Create git commits for dotfiles changes, grouping by component with conventional prefix style
| name | create-commit |
| description | Create a Jujutsu (jj) commit with a concise message |
When the user asks you to create a new commit, follow these steps to create a commit using Jujutsu (jj):
jj describe to set commit messages (opens interactive editor)Run these jj commands in parallel:
jj status # See all changes in working copy
jj diff # See detailed changes
jj log -r 'ancestors(@, 3)' # See recent commits for style reference
Draft a concise commit message (1-2 sentences explaining what changed and why), then use:
jj describe -m "$(cat <<'EOF'
[Your drafted message here]
EOF
)"
After describing the commit, always create a new empty revision on top:
jj new
Run jj log -r 'ancestors(@, 3)' to confirm the commit and new revision were created successfully.
/Users/meain/dev/veeam/), use meain/ prefix for branch namesmeain/earn-prod-adx-sku-downsize, meain/fix-auth-bug