메뉴
Walk through open Sentry issues for tooll3, latest first, proposing a fix and committing each one separately with user review between. Use when the user wants to triage Sentry, fix Sentry issues, work through the Sentry backlog, or invokes /sentry-fix.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/tixl3d/tixl --skill sentry-fix명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Extract a comprehensive operator-mention analysis from each new video transcript. Reads the SRTs in .help/.tmp/video-transcripts/ (produced by video_to_srt.py), and for each one without an analysis yet, writes references/video-analysis/<id>.md — every meaningful operator discussion with its timestamp, depth, and a one-line note. Feeds the editor's deep-link index; never touches the wiki, the YouTube descriptions, or git. Use when the user wants to analyze transcribed videos, build the operator mention index, or invokes /analyze-videos.
Draft the embedded help text for ui: topics whose doc is still empty. For each topic it gathers the transcript passages where the maintainer explains it (via the ui: deep-link index), the implementing class, and any existing .help/ page, then distills a short user-facing doc into .help/references/topics/ui-topics.md. Use after the videos are transcribed and analyzed (stage 2), when the user wants to write or fill in the ui topic docs.
Unattended batch over the "In progress" column of the TiXL road-map GitHub board. Implements straightforward tickets as individual git stashes and writes plans for the rest as files in .agentic/Plans/ — no questions, no commits, no GitHub writes. Use when the user wants to work through their In-progress tickets, process the board backlog, or invokes /process-tickets.
SOC 직업 분류 기준
| name | sentry-fix |
| description | Walk through open Sentry issues for tooll3, latest first, proposing a fix and committing each one separately with user review between. Use when the user wants to triage Sentry, fix Sentry issues, work through the Sentry backlog, or invokes /sentry-fix. |
Drive a review-gated loop over open Sentry issues for the tooll/tooll3 project. One commit per issue, user reviews between each.
.env at repo root. If SENTRY_AUTH_TOKEN= is empty or the file does not exist, stop and tell the user:
event:read and event:write scopes. event:read covers listing/fetching; event:write is required to mark issues resolved at hand-off..env.example to .env and paste the token in.Scripts/sentry-issues.ps1 exists. If not, the skill is incomplete — tell the user.If a -Resolve call returns 403 Forbidden, the token is read-only — tell the user to regenerate it with event:write (Sentry doesn't allow editing scopes after creation).
Do not store the token, do not echo it, do not print it.
Run:
.\Scripts\sentry-issues.ps1 -List -Limit 25
That returns slimmed JSON, latest-lastSeen first. Parse it.
Show the user a compact table — short ID, title, level, count, lastSeen — and ask them to confirm they want to start with #1, or pick a different issue / skip filter. Do not auto-start without a confirm; some issues may be already-known noise.
If the list is empty, say so and stop.
For the chosen issue:
.\Scripts\sentry-issues.ps1 -Issue <numericId>
This returns { issue, event }. The interesting bits:
issue.title, issue.culprit, issue.metadataevent.entries[?type=='exception'].data.values[*].stacktrace.frames — frames with filename, function, lineNo, inAppevent.tags — release, environment, os, runtimeevent.contexts — useful runtime/device contextSentry stack-trace filenames look like D:\a\tixl\tixl\Core\Operator\Symbol.cs (CI build path) or relative like Gui\Windows\SymbolLib\NamespaceTreeNode.cs. To resolve:
D:\a\tixl\tixl\) — what remains is repo-relative.\ to / if needed for the Read tool.lineNo from Sentry is 1-based and lines up with the file in main.Read the named function plus ~20 lines of surrounding context. Read every inApp: true frame from the top of the stack until you've understood the trigger. Stop reading once you have enough to explain the cause — don't open every frame in the trace.
Write a short root-cause statement to the user — 2-4 sentences. State which null reference, which invariant was broken, which input was unexpected. Cite the exact file:line you read. If you genuinely can't determine the cause from the trace (missing context, intermittent timing bug, third-party code), say so and ask if the user wants to skip or annotate the issue in Sentry instead of fixing blind.
Describe the fix in 1-3 bullets before editing. Mention:
Wait for user "go" / "yes" / "do it" — or pushback. Do not edit without an ack.
Edit minimally. Follow .agentic/AGENT_INSTRUCTIONS.md rules:
.cs files unless the file is LF.Identify the project from the changed file's path (Core, Editor, Operators/Lib, etc.) and run:
dotnet build <project>.csproj
If the build fails, fix the build error before continuing. Do not hand off a broken build for review.
The user commits the change themselves, so they're forced to review every diff before it lands. After the build is green:
Run git status --short and git diff --stat so the user sees what they're reviewing.
Draft a suggested commit message in a fenced block (don't run git commit). Format:
<area>: <one-line fix summary>
Fixes Sentry tooll3 issue <SHORT-ID> (<permalink>).
<2-4 lines: what was happening, what the fix does, any caveats.>
Examples of <area>: Core, Editor, Operators, Gui. Match the project root the file lives in. Do not include Co-Authored-By unless the user has asked for it project-wide — check git log for the recent convention.
State the next issue from the list (short-ID + title) so the user knows what's queued.
Stop and wait. Do not run git commit, git add, or move to the next issue. End the hand-off message with the question:
Resolve Sentry
<SHORT-ID>as fixed-in-next-release? Replynextto mark resolved and continue,next noresto continue without resolving, orskip/revert/stop.
User reply mapping:
next / yes / continue — first run Scripts\sentry-issues.ps1 -Resolve <numericId> -InNextRelease, then proceed to the next issue (step 2a). Sentry auto-resolves on the next release tag and auto-reopens as a regression if it recurs.next nores / next no — proceed to the next issue without resolving. Use this when the user committed but isn't confident enough to mark resolved (e.g. wants to manually verify first).skip — drop the current next-issue, present the one after. Don't resolve.revert / undo — they've reverted the working-tree edit themselves; re-examine or move on. Don't resolve.stop — end the session. Don't resolve.If the user only says next without any explicit yes/no on resolution, treat it as the default (next = resolve). If they previously said next nores for some issues, don't assume that sticks for the next one — re-ask each time.
If the user says nothing or asks a question, answer the question and stay paused.
Some issues aren't fixable from TiXL's code: driver bugs (DXGI E_NOTIMPL), library version mismatches we don't control, user environment problems (missing .NET runtime on the target machine in a way TiXL can't detect), broken installs we can't recover. For these, mark the issue archived on Sentry instead of resolved-in-next-release:
.\Scripts\sentry-issues.ps1 -Archive <numericId>
Sentry hides archived issues from the default unresolved view. They auto-reopen if Sentry's "escalation" detector decides the issue has become significant again (e.g. starts hitting a much wider user base). The right surface for "won't fix from our side."
When triaging, propose Archive rather than Resolve for clearly out-of-our-hands cases, and let the user confirm.
git commit or git add — the user commits themselves so they're forced to review every diff.git push).next / yes at step 2h. The hand-off question is the trigger; silence is not consent.Resolve an issue we didn't actually fix — that falsely claims a fix landed and will mark it as a regression when it recurs. Use Archive for won't-fix.(12 additional frames were not displayed) and you need them, ask the user to open the issue in the Sentry web UI and paste the full trace.git worktree. The project explicitly forbids worktrees (see .claude/CLAUDE.md).Stop the loop and report up if:
.agentic/Plans/, and move on or stop.