القائمة
Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity. Use when invoked as `$work-track` or when the user asks to track a work item.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
End-of-day — draft and post daily comments for tracked tickets missing a comment
Morning startup workflow for daily notes, yesterday summary, agenda, status comments, meeting sections, and daily branch setup. Use when invoked as `$work-start` or when the user asks to start the work day.
Start work on a Linear ticket by gathering context, planning, creating a branch/worktree, implementing, testing, opening a draft PR, and updating Linear. Use when invoked as `$linear-plan` or when the user asks to start a Linear ticket.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Load the shared skill from ~/.agents/skills/linear-plan/SKILL.md.
| name | work-track |
| description | Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity. Use when invoked as `$work-track` 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` ` 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.