deslop
Remove AI-generated code slop from current branch
What this skill does
# Remove AI Code Slop
Check the diff against main and remove AI-generated slop introduced in this branch.
## Step 1: Get changed files
```bash
git diff main --name-only
```
If an argument was provided, focus only on that file.
Great, now I want you to carefully read over all of the new code you just wrote and other existing code you just modified with "fresh eyes"
## Step 2: For each file, compare with original
For each changed file:
1. Read the current version
2. Get the original from main: `git show main:<filepath>`
3. Compare style, patterns, and conventions, looking super carefully with "fresh eyes" for any obvious bugs, errors, problems, issues, confusion, etc.
## Step 3: Remove slop
Use Edit tool to remove:
**Unnecessary comments:**
- Comments explaining obvious code (`// increment counter`, `// return the result`)
- Comments that weren't in the original and add no value
- Comments inconsistent with the file's existing style
- Redundant JSDoc/docstrings on simple functions
**Defensive over-engineering:**
- Try/catch blocks around code that can't throw
- Null checks on values already validated upstream
- Defensive checks in internal/trusted code paths
- Unnecessary `|| []` or `?? {}` defaults not present in similar code
**Type hacks:**
- `as any` or `as unknown` casts
- `@ts-ignore` / `@ts-expect-error` without clear reason
- `!` non-null assertions that hide real issues
**Style inconsistencies:**
- Verbose patterns when the file uses terse style
- Different naming conventions than the rest of the file
- Extra blank lines or formatting differences from original
**Over-abstraction:**
- Helper functions used only once
- Unnecessary intermediate variables
- Overly generic code for specific use cases
**General:**
- Carefully fix anything you uncover
## Step 4: Report
Output ONLY a 1-3 sentence summary. No bullet points, no file lists, no explanations.
Example: "Removed 4 redundant comments and 2 unnecessary null checks. Simplified error handling in auth.ts."
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.