Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity. Use when invoked as `$work-track-item` or when the user asks to track a work item.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Add or update a Linear ticket or GitHub PR in today's daily note. Each item gets an H2 section with inline fields and timestamped activity.
On macOS, run every linear ... command outside the sandbox on the first
attempt so the CLI can access credentials stored in the system keychain. Use
scoped escalation with prefix_rule: ["linear"]. If a sandboxed command
reports No keyring entry or No API key configured, retry outside the
sandbox before asking the user to authenticate. Never print, log, or expose
linear auth token or an API key.
Accept:
DXO-71 or DEVX-943.getditto/ditto#23274.If the user provides only a number, assume DXO-<number>.
Locate today's note:
today_date=$(date +%Y-%m-%d)
today_day=$(date +%A)
today_year=$(date +%Y)
note_path="$HOME/2ndBrain/daily-notes/${today_year}/${today_date} ${today_day}.md"
If missing, tell the user to run $work-start first.
Fetch item details:
linear issue view. Extract identifier, title, state, and URL.gh pr view <target> --json number,title,state,url,repository,headRefName.Search for an existing section:
grep -nE "^## .*${TICKET_ID}( |$)" "${note_path}"
grep -nE "^## .*#${PR_NUMBER}( |$)" "${note_path}"
If a section exists:
status:: if changed.- \HH:MM` <note>` before the next H2 or section boundary.If no section exists, insert a block:
## <TICKET-ID> <title-slug>
ticket:: [<TICKET-ID>](<linear-url>)
pr:: [#<number>](<github-pr-url>)
branch:: `<headRefName>`
status:: <current-state-lowercase>
commented:: false
- `HH:MM` <notes or generated activity>
Omit fields that do not apply, except commented:: false should be present for Linear-tracked work.
Formatting rules:
key:: value on its own line.<!-- track-work:items --> when present, otherwise before the --- preceding # Meetings.Report item, status, PR/branch if known, and the note that was appended.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Quick-save the last assistant response as a verbatim note in the 2ndBrain Obsidian vault (~/2ndBrain/quick-notes/<year>/). Use when the user asks to quick-save/save the last response to 2ndBrain, or invokes $2ndbrain or /skill:2ndbrain.
日本語の概要は準備中です。原文の説明を表示しています。
Write commit messages under the agent-commits convention - a Conventional Commits fork with no chore catch-all, intent-only type tokens, facts in trailers, and legally-grounded AI provenance (Assisted-by, never Co-authored-by). Use when composing a commit in a repo whose commitlint.config.js extends agent-commits, when deciding between feat/fix/refactor/perf, or when recording AI participation.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate multi-agent work through durable artifacts in git instead of chat. Use this whenever a task involves sending a message to another agent, agent mailboxes or handoffs, claiming work from a shared queue, notifying another agent or crew (OpenClaw, Grok Bot, Claude Code, Codex, Gas Town/Gas City workers) that work is ready, or whenever the user mentions the artifact bus, message bus, agent mail, beads mail, doorbells, or pings between agents — even if they don't say "bus" explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Use aven to find tasks, update status, and leave durable handoff context.
日本語の概要は準備中です。原文の説明を表示しています。
Claude Code workflow tips from Boris Cherny (creator of Claude Code) and the Claude Code team. Use when: setting up Claude Code, optimizing workflows, running parallel sessions, configuring CLAUDE.md, using skills/commands, subagents, hooks, MCP integrations, or learning best practices. Covers: git worktrees, plan mode, verification, permissions, Slack MCP, BigQuery, prompting tips, plugins, custom agents, sandboxing, keybindings, status lines, output styles, customization, /simplify for code quality, /batch for parallel code migrations, /loop for scheduled tasks, code review agents, /btw for mid-task questions, /effort max reasoning, remote control sessions, voice mode, setup scripts, session naming, /color, PostCompact hook, auto mode, /schedule cloud jobs, iMessage plugin, auto-memory, and auto-dream, mobile app, session teleporting, Cowork Dispatch, Chrome extension, Desktop app, /branch forking, --bare SDK startup, --add-dir multi-repo, --agent custom agents, /voice input.
日本語の概要は準備中です。原文の説明を表示しています。
Codex workflow tips from Boris Cherny (creator of Codex) and the Codex team. Use when: setting up Codex, optimizing workflows, running parallel sessions, configuring AGENTS.md, using skills/commands, subagents, hooks, MCP integrations, or learning best practices. Covers: git worktrees, plan mode, verification, permissions, Slack MCP, BigQuery, prompting tips, plugins, custom agents, sandboxing, keybindings, status lines, output styles, customization, /simplify for code quality, /batch for parallel code migrations, /loop for scheduled tasks, code review agents, /btw for mid-task questions, /effort max reasoning, remote control sessions, voice mode, setup scripts, session naming, /color, PostCompact hook, auto mode, /schedule cloud jobs, iMessage plugin, auto-memory, and auto-dream, mobile app, session teleporting, Cowork Dispatch, Chrome extension, Desktop app, /branch forking, --bare SDK startup, --add-dir multi-repo, --agent custom agents, /voice input.
日本語の概要は準備中です。原文の説明を表示しています。