القائمة
Query PostHog error tracking and Sentry issues from the command line. Use when asked what errors are happening, which errors are being missed or untriaged, for production error rates or impact by user, or whenever posthog-cli or sentry-cli is mentioned.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Capture and persist browser screenshots or GIFs for visual review of a web UI. Use when verifying a UI change visually, reviewing a page's design or layout, recording a multi-step interaction (dropdown, hover, form flow), toggling dark mode for a comparison shot, or when a screenshot needs to be written to disk rather than only shown inline.
Run and troubleshoot copier updates in a project generated from one of the user's templates, and maintain the templates themselves. Use when a task mentions copier, copier update, .copier-answers.yml, .rej files after an update, ctt or copier-template-tester, or one of calcipy_template, mdformat-plugin-template, my_go_template, or app-template.
Audit or write an hk.pkl config (jdx/hk git hooks). Use when creating hk.pkl, upgrading the pinned hk version, adding a linter step, or when fixes made by a pre-commit hook are not being staged. Covers version pinning, staging semantics, builtins, and DRY structure.
Work a multi-phase plan to completion with subagents, checkpoint commits, and questions back to the user. Invoke explicitly with a plan document.
Async Python conventions and footguns — asyncio.TaskGroup over gather, event-loop-bound primitives, offloading blocking work to threads or processes, cancellation across the thread boundary, and dedicated executors. Use when writing or reviewing async def, await, asyncio.to_thread, run_in_executor, create_task, async generators, or when diagnosing a stalled event loop, a "bound to a different event loop" error, or latency that only appears under load.
The user's full writing system for prose they author — README and docs text, landing copy, PR and commit descriptions, Linear proposals, design docs, Slack and email messages. Use when drafting or rewriting any human-facing prose, when a draft reads like AI wrote it, when stripping AI slop from documentation, or when relaying research output into a human-facing surface. CLAUDE.md carries the compressed rules; this carries the reasoning, the before/after pairs, and the per-format shapes.
| name | observability-clis |
| description | Query PostHog error tracking and Sentry issues from the command line. Use when asked what errors are happening, which errors are being missed or untriaged, for production error rates or impact by user, or whenever posthog-cli or sentry-cli is mentioned. |
Both tools have quirks that waste turns if rediscovered. Org and project slugs are
project-specific — check that project's CLAUDE.local.md.
The binary is posthog-cli, installed via mise. The agent-first surface is
posthog-cli api:
posthog-cli api search <regex> # find tools
posthog-cli api info --json <tool> # get a schema
posthog-cli api call --json <tool> '<json>' # run one
For "what errors are happening" or "what is being missed", use
query-error-tracking-issues-list. It defaults to active issues, the last 7 days,
sorted by occurrences, with test accounts filtered out.
For impact rather than volume:
posthog-cli api call --json query-error-tracking-issues-list \
'{"dateRange":{"date_from":"-30d"},"orderBy":"users"}'
assignee: null across the board means nobody is triaging.
sentry-cli uses a personal read token in ~/.sentryclirc.
The --org flag goes after the subcommand, not before:
sentry-cli projects --org <org> list
There is no issues-list subcommand. Query issues through the REST API with the same token, read from the file inline so the literal stays out of shell history and transcripts:
curl -H "Authorization: Bearer $(sed -n 's/^token=//p' ~/.sentryclirc)" \
"https://sentry.io/api/0/projects/<org>/<project>/issues/?statsPeriod=24h&query=is:unresolved&sort=freq&limit=15"
Useful query filters: is:unresolved, an endpoint path, N+1.
Parse responses with json.loads(..., strict=False). Bodies contain raw control
characters inside SQL strings and strict parsing fails on them.