incident-triage
Skill16k starsChanged 15 days agoMITView on GitHub
First-pass triage of a possible production incident for Paradev's hosted services. Gathers signals (recent deploys, Sentry spikes, health checks), proposes a severity and a status.paradev.com message, then stops for human approval. Use when someone reports an outage, errors spike, or asks "is something down?".
23 other projects use a version of this; 1 new project in the last 4 weeks, against 0 the 4 before.
Adopted by
Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- termalinapp/termalin-plugintheir own version, first seen Nov 15, 2026
- briiirussell/cybersecurity-skillstheir own version, first seen Nov 1, 2026
- Happy-Technologies-LLC/happy-platform-skillstheir own version, first seen Nov 1, 2026
- rpraharaj/ai-sdlctheir own version, first seen Nov 1, 2026
- rpraharaj/ai-engineertheir own version, first seen Nov 1, 2026
- ParadevAI/Paradevword for word, first seen Nov 1, 2026
Who's talking about superset-sh/superset
- Paradev“Introducing Superset”YouTube · Feb 27, 2026 · 13k views
- Paradev“What is Superset in 60s?”YouTube · Jan 3, 2026 · 5.6k views
- Repocast | GitHub 일일 브리핑“AI 에이전트 IDE, Superset으로 생산성 10배 올리기!”YouTube · Mar 1, 2026 · 2.7k views
- Gourcer“superset-sh/superset - Gource visualisation”YouTube · Mar 1, 2026 · 1k views
- DevDrop“Superset: Run an Army of Claude Code Agents in Parallel”YouTube · May 14, 2026 · 422 views
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub, Bluesky, YouTube, Hacker News and the web (50 times).
On GitHub · 20
- Mar 18, 2026[bug] unable to create worktree from existing branch — ParadevAI/Paradev14 reactions · 6 comments
- Oct 25, 2026"Use this instead of publishing a Claude artifact whenever the reader is a teammate" — ParadevAI/Paradev3 reactions · 2 comments
- Mar 24, 2026Feat/linux desktop support — ParadevAI/Paradev2 reactions · 10 comments
- Jan 9, 2026[Question]: How is OMOC compared to the other OpenCode tools? — code-yeongyu/oh-my-openagent2 reactions · 2 comments
- Oct 27, 2026chore(marketing): say Paradev in marketing, email, and agent docs copy — ParadevAI/Paradev1 reaction · 3 comments
15 more on GitHub
- Oct 27, 2026docs(marketing): show the former name in structured data and llms.txt — ParadevAI/Paradev1 reaction · 4 comments
- Oct 20, 2026chore(desktop): bundle pdev 0.1.5 — ParadevAI/Paradev1 reaction · 3 comments
- Oct 6, 2026chore(dev): isolate the pinned PostgreSQL 18 development volume — ParadevAI/Paradev1 reaction · 2 comments
- Oct 6, 2026fix(desktop): allow configured S3 upload origins in CSP — ParadevAI/Paradev1 reaction · 2 comments
- Oct 1, 2026fix(desktop): stop links from swallowing text typed after a URL — ParadevAI/Paradev1 reaction · 3 comments
- Sep 9, 2026Changes pane fails to refresh and displays stale diffs after committing and making follow-up changes — ParadevAI/Paradev1 reaction · 1 comment
- Sep 4, 2026chore(desktop): bump version to 1.26.0 — ParadevAI/Paradev1 reaction · 3 comments
- Jun 24, 2026feat(sidebar): show worktrees symlinked into a project's dependencies — ParadevAI/Paradev1 reaction · 3 comments
- Apr 8, 2026feat(desktop): workspace number badges on modifier hold — ParadevAI/Paradev1 reaction · 5 comments
- Mar 27, 2026Support independent working trees? — siteboon/claudecodeui1 reaction · 1 comment
- Mar 8, 2026[bug] github no longer connected (1.0.7 => 1.1.2) — ParadevAI/Paradev1 reaction · 1 comment
- Mar 6, 2026[bug][security] Masked terminal input (passwords) leaked into tab titles via commandBuffer — ParadevAI/Paradev1 reaction · 2 comments
- Oct 14, 2026Forgejo/codeberg support — ParadevAI/Paradev0 reactions · 1 comment
- Oct 12, 2026Add Superset agent workspace detection — auron-labs/harness-detect0 reactions
- Oct 10, 2026feat(desktop): add an optional centered reading width for terminal panes — ParadevAI/Paradev0 reactions · 1 comment
On Bluesky · 14
- Mar 2, 2026Turn your terminal into a coding agent command center - run Claude Code, Codex, and 10+ AI agents simultaneously with git worktree… — @arifsolmaz.bsky.social4 likes and reposts · 1 reply
- Feb 28, 2026🔥 Hot Repo! 🔥 (100+ new stars) 📦 superset-sh / superset ⭐ 2,233 (+156) 🗒 TypeScript IDE for the AI Agents Era - Run an army of Claude… — @github-trending-js.bsky.social4 likes and reposts
- May 24, 2026Parallel agent execution is smart – but the real win here is finally getting proper observability into what these coding agents are… — @sirile.bsky.social3 likes and reposts · 2 replies
- May 23, 2026Superset is an open-source IDE for running multiple AI coding agents in parallel on macOS. — @druce.ai3 likes and reposts
- Sep 2, 2026📦 superset-sh / superset ⭐ 13,646 (+48) 🗒 TypeScript Superset is an agentic IDE to orchestrate 100+ coding agents in parallel. Run any… — @github-trending-js.bsky.social2 likes and reposts
9 more on Bluesky
- May 25, 2026📦 superset-sh / superset ⭐ 11,101 (+64) 🗒 TypeScript Code Editor for the AI Agents Era - Run an army of Claude Code, Codex, etc. on your… — @github-trending-js.bsky.social2 likes and reposts
- Mar 21, 2026the bottleneck with AI coding agents was always "one task at a time." Superset runs 10+ agents in parallel, each in its own git worktree so… — @ai-nerd.bsky.social2 likes and reposts
- Mar 6, 2026Superset : un terminal turbochargé pour faire tourner une équipe d'agents IA de code en parallèle (Claude Code, Codex…). Chaque agent… — @camilleroux.com2 likes and reposts · 1 reply
- May 22, 2026⚡ ALPHA · score 8/10 Launch HN: Superset (YC P26) – IDE for the agents era https://github.com/superset-sh/superset — @alpha-pipeline.bsky.social1 likes and repost
- Apr 9, 2026🔥 Hot Repo! 🔥 (100+ new stars) 📦 superset-sh / superset ⭐ 9,006 (+192) 🗒 TypeScript Code Editor for the AI Agents Era - Run an army of… — @github-trending-js.bsky.social1 likes and repost
- Mar 5, 2026🎉 Celebrating! 🎉 (500+ new stars) 📦 superset-sh / superset ⭐ 4,675 (+795) 🗒 TypeScript IDE for the AI Agents Era - Run an army of… — @github-trending-js.bsky.social1 likes and repost · 1 reply
- Mar 2, 2026github.com/superset-sh/sup... GitHub - superset-sh/superset: IDE for the AI Agents Era - Run an army of Claude Code, Codex, et... — @technews4869.bsky.social1 likes and repost
- Feb 28, 2026🔥 Hot Repo! 🔥 (100+ new stars) 📦 superset-sh / superset ⭐ 2,233 (+156) 🗒 TypeScript IDE for the AI Agents Era - Run an army of Claude… — @github-trending.bsky.social1 likes and repost
- May 23, 2026📰 Superset, an open-source agentic IDE for running coding agents like Claude Code and Codex in parallel, has been launched by Avi, Kiet,… — @sagalinked.bsky.social0 likes and reposts · 1 reply
On YouTube · 13
- Feb 27, 2026Introducing Superset — Paradev13k views · 7 comments
- Jan 3, 2026What is Superset in 60s? — Paradev5.6k views · 2 comments
- Mar 1, 2026AI 에이전트 IDE, Superset으로 생산성 10배 올리기! — Repocast | GitHub 일일 브리핑2.7k views · 1 comment
- Mar 1, 2026superset-sh/superset - Gource visualisation — Gourcer1k views · 2 comments
- May 14, 2026Superset: Run an Army of Claude Code Agents in Parallel — DevDrop422 views
8 more on YouTube
- Mar 24, 2026You're Not Using AI Agents Efficiently (Here's Why) — Dhaval Bhatt | AI Product Accelerator211 views · 1 comment
- Mar 6, 2026Superset — Open Source Scribes82 views
- Aug 2, 2026Superset: Give Every Coding Agent Its Own Worktree — BACKFIRED X78 views · 1 comment
- May 27, 2026GitHub - superset-sh/superset: IDE for the AI Agents Era - Run an army of Claude Code, Codex, etc... — GitHub Daily Trend AI Podcast47 views
- Mar 7, 2026This Repo Got 7.3K Stars in 4 months — Here's Why 🔥 #Superset #AgenticAi #AiAgents #ClaudeCode #Cli — Pulse39 views · 1 comment
- Jun 26, 2026Claude Code, Codex e Cursor — superset-sh/superset orquestra agentes #AI #Shorts — RepoShots34 views · 1 comment
- May 19, 2026Superset — Open Source Scribes22 views
- May 22, 2026Synthetic Signal - Afternoon - May 22, 2026 — Synthetic Signal0 views
On Hacker News · 2
- May 22, 2026Launch HN: Superset (YC P26) – IDE for the agents era108 points · 135 comments
- Dec 1, 2025Show HN: Superset – Run 10 parallel coding agents on your machine24 points · 3 comments
On the web · 1
- Nov 9, 2026100개 이상의 AI 코딩 에이전트를 병렬로 실행하는 개발자용 ... — gitbap.com
Used with
Projects with it also use write-runbook, threat-hunting and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MaheshAwasareSkillwrite-runbook
Generate an operational runbook for a service from its code, config, and dependencies — what to do when it breaks, where to look, how to roll back, who to escalate to. Use proactively before a service goes to production, after a major incident, or when handing off operational ownership.
Also in 3 projects that use this
allanninalSkillthreat-hunting
Hunt threats using Sigma detection rules and security analysis techniques. Use when investigating security incidents, creating detection rules, or analyzing suspicious activity.
Also in 3 projects that use this
srclightSkillexplore-codebase
This skill should be used when the user asks to "explore this codebase", "understand this project", "give me an overview", "how does this work", "onboard me", "walk me through the architecture", "map the codebase", or any request to understand a codebase's structure, architecture, or design.
Also in 3 projects that use this
thlaureSkillreview-change
Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.
Also in 4 projects that use this
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 3 projects that use this
SentrySkillsecurity-review
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Also in 4 projects that use this
Other versions23 projects use a version of this.
Word for word · 1
- ParadevAI/Paradev★ 16k100% same
Edited · 0
None found.
Wrote their own version · 22
- briiirussell/cybersecurity-skills★ 489same name
- Happy-Technologies-LLC/happy-platform-skills★ 41same name
- Indium-AI-Labs/indium-agentkit★ 18same name
- Ionate-Technologies/indium-agentkit★ 17same name
- Mozurok/fhorja.dev★ 10same name
- aws-samples/sample-aws-ops-skills-for-agents★ 8same name
- ByronScottJones/Agents★ 7same name
- aprameyak/coding-skills★ 1same name
- natrisc/claude-code-agents★ 1same name
- pinexai/claude-code-skills★ 1same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- autumnSkill
- cdp-verificationSkill
- db-migrationsSkill
- decideSkill
- dev-doctorSkill
- mobile-android-verificationSkill
- mobile-demo-filmSkill
- mobile-demo-recordSkill
- mobile-eas-devSkill
- mobile-sim-verificationSkill
- redesignSkill
- superset-settingsSkill
- ticket-formatSkill
- trpc-compatSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Read-only. Do not deploy, roll back, disable workflows, change flags, resolve Sentry issues, or run SQL that writes.
- Distinctive: line 16
Do not post to status.paradev.com, Slack, Discord, Plain, X, or any other channel.
- Distinctive: line 18
If a tool is not connected or a check fails, write "not checked" and the reason.
- Distinctive: line 19
Use UTC times everywhere.
- Distinctive: line 23
Write one line each:
- Distinctive: line 26
When it started (first report, or first signal you find).
- Very specific: line 29
If only one user or one machine is affected, stop here.
- Distinctive: line 34
Run the checks that can run in parallel at the same time.
- Distinctive: line 44
Sentry: Use the Sentry MCP tools when they are connected.
- Distinctive: line 93
Wait for the human. If they approve the message, they post it in incident.io themselves.
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Incident triage
You gather facts and draft. A human decides and posts. The runbook is
docs/runbooks/incidents.md; read its "Severity" and "Status page updates" sections before you
start.
Rules
- Read-only. Do not deploy, roll back, disable workflows, change flags, resolve Sentry issues, or run SQL that writes.
- Do not post to status.paradev.com, Slack, Discord, Plain, X, or any other channel. Do not declare an incident. Your output is a draft in this conversation.
- If a tool is not connected or a check fails, write "not checked" and the reason. Do not guess.
- Use UTC times everywhere.
1. Frame the report
Write one line each:
- What users see, in their words.
- When it started (first report, or first signal you find).
- Who is affected: everyone, one region, one feature, one version, or one user.
If only one user or one machine is affected, stop here. Tell the human that this is a support
issue, and suggest the superset:doctor skill (and superset status for host state).
2. Gather signals
Run the checks that can run in parallel at the same time. Record each result with its time.
- Recent deploys
For a run near the start time, look at the failed or slow jobs, especiallygh run list --workflow "Deploy Production" --limit 5 \ --json databaseId,headSha,status,conclusion,createdAt,updatedAt git log --since="6 hours ago" --oneline origin/maindeploy-database(migrations):gh run view <id> --json jobs. - Sentry. Use the Sentry MCP tools when they are connected. Search for issues first seen or spiking in the last 2 hours, in every project: api, web, admin, marketing, docs, relay (it also holds realtime), sandbox, desktop, host-service, mobile. For each match, record the issue title, event count, first-seen time, and the release.
- Health checks (GET only, 10-second timeout):
Expected: relaycurl -sS -m 10 -w ' %{http_code} %{time_total}s\n' https://relay.superset.sh/health curl -sS -m 10 -w ' %{http_code} %{time_total}s\n' https://realtime.superset.sh/health curl -sS -m 10 -w ' %{http_code} %{time_total}s\n' https://api.superset.sh/api/health{"ok":true,"proto":2}200, realtime{"ok":true}200, API{"ok":true,"database":"ok"}200. A 503 from the API names the database state. Any other 5xx or a timeout is a failure. Also readhttps://status.paradev.com/api/v2/summary.jsonto see what the page shows now. - Vercel (if the CLI is linked):
vercel lsfor recent production deploys, andvercel logs <deployment-url>for errors around the start time. - Upstream status. Name the upstream provider that the signals point to (Vercel, Cloudflare, Neon, GitHub), and ask the human to check its status page. Do not fetch those pages yourself unless the human asks.
3. Propose
Reply with this block and nothing after it:
## Triage draft (not posted)
Summary: <one line: what is broken, since when, for whom>
Signals
- Deploys: <result>
- Sentry: <result>
- Health: relay <code>, realtime <code>, api <code>
- Vercel: <result or "not checked: reason">
- Likely cause: <one line, or "unknown">
Proposed severity: SEV<1|2|3> — <one-line reason from the runbook table>
Proposed status.paradev.com update (<Investigating|Identified|Monitoring|Resolved>):
> <message from the runbook template, filled in>
Suggested next steps for the lead:
1. <for example "roll back deployment X with vercel rollback">
2. ...
Waiting for approval. I have not posted, deployed, or changed anything.4. Stop
Wait for the human. If they approve the message, they post it in incident.io themselves. If they ask for a change, redraft and stop again. This skill stays read-only after approval. A rollback or any other write action is a separate request outside this skill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

