profile-blocking-and-locking
Skill1 starsChanged 5 months agoAGPL-3.0View on GitHub
Use when stapler-squad stalls, hangs, or has p99 latency spikes and you must find what is blocked and why, then reduce it. Triggers - lock contention, mutex wait, blocked goroutines, deadlock, hang, stall, stuck request, semacquire, sync.Mutex, channel block, goroutine leak, head-of-line blocking, scheduler latency, run queue, tmux exec gate wait, ws-unary or terminal-mux queueing, "UI freezes", "why is it slow under load". Also: goroutine dump, pprof mutex/block, frozen/unresponsive UI, RWMutex, WaitGroup, `all goroutines are asleep`. For SQLite pool waits use profile-db-usage (PR #1341); for plain CPU/alloc hotspots use perf:make-it-faster or go:optimize; to choose a primitive use golang-concurrency.
In this repository19 other files it gives its agents.
- website/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ponytailSkill
- backlog-feature-improvementSkill
- commit-verify-syncSkill
- deterministic-fast-testsSkill
- e2e-test-conventionsSkill
- fix-flaky-tests-dont-deferSkill
- git-history-cutoverSkill
- github-issue-to-backlogSkill
- interface-pollution-checklistSkill
- observability-grafana-dashboardsSkill
- observability-victoriametrics-tempoSkill
- prefer-go-git-over-subshellsSkill
- primitive-obsession-checklistSkill
- profile-db-usageSkill
- rollout-readiness-reviewSkill
- stapler-squad-rulesSkill
- worktree-disk-cleanupSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.