technical-deslop
Technical Deslop
Purpose
Clean branch/staged diffs by removing AI-style slop and restoring repo-consistent style without changing behavior.
When to use
- A diff feels over-explained, overly defensive, or inconsistent with surrounding code.
- You need a final cleanup pass before review/PR.
- You want to normalize style after automated generation.
Workflow
More from vincentkoc/dotskills
technical-documentation
Build and review high-quality technical docs as well as agent instruction files in your repository.
121technical-skill-finder
Mine coding agent logs (Codex/Cursor/session histories and similar telemetry) to discover high-value candidate skills, then draft structured skill creation/reuse recommendations.
62technical-integrations
Hunt existing integration patterns and design vendor/framework-agnostic API, RFC, SDK, and integration plans for new external vendor integrations.
61opik-optimizer
Optimize LLM prompts, tools, and agents in Opik using standardized optimizer workflows (prompt optimization, tool optimization, and parameter tuning), dataset/metric wiring, and result interpretation.
36example-skill
Template skill for repository authors; excluded from public publishing.
34opik-integrations-auditor
Audit, compare, and document Opik integrations across Python SDK, TypeScript SDK, and OTEL/API backend. Use when adding a new integration, reviewing an existing one, or generating first-pass integration docs and gap analysis.
33