emiliodoming
6 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
emiliodominguezflow-benchmark
Performance measurement with a reproducible baseline and stated uncertainty. Use before optimizing, or to compare alternatives on speed, memory or size. Feeds flow-work or flow-refactor with evidence.
- installs
- 1
- GitHub stars
- 1
- Updated
- Sep 27
emiliodominguezflow-commit
Conventional commit messages and atomic commits. Use when asked only for a commit message or a commit; message-only requests never touch Git. Hands off to flow-ship when a push or review request was asked for.
- installs
- 1
- GitHub stars
- 1
- Updated
- Sep 27
emiliodominguezflow-diagnose
Root-cause investigation for hard failures. Use when a bug, regression or crash in the product has no obvious cause, or a first fix did not hold. Hands off to flow-work or flow-triage.
- installs
- 1
- GitHub stars
- 1
- Updated
- Sep 27
emiliodominguezflow-observe
Observability for a service or feature: structured logs, metrics, traces and alerts tied to user impact. Use when adding telemetry or alerts, before a launch, or after an incident lacked signal. Feeds flow-triage and flow-diagnose.
- installs
- 1
- GitHub stars
- 1
- Updated
- Sep 27
emiliodominguezflow-prune-agent-setup
Audit and tidy a coding agent's configuration: instructions, memory, settings, hooks, MCP servers and plugins. Use when that setup has grown noisy, conflicting or stale. Feeds flow-handoff.
- installs
- 1
- GitHub stars
- 1
- Updated
- Sep 27
emiliodominguezflow-simplify
Targeted cleanup of provably dead code and accidental complexity. Use for dead paths, needless indirection or generated slop, not redesign. Hands off to flow-review or flow-refactor.
- installs
- 1
- GitHub stars
- 1
- Updated
- Sep 27