bsene/skills

show-me-the-code

Enforces one rule: every code change must be presented as a unified diff (diff -u format) with 3 lines of context.

Ver código fuente
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Show Me The Code

Rule: every code change → unified diff (diff -u format). No exceptions.

  • 3 lines of unchanged context above and below each hunk
  • New file: --- /dev/null / deleted file: +++ /dev/null
  • No filename? Use a/snippet.ts
  • Multiple files: one diff block per file

After the diff: optional 1–3 sentence why.

Example

Asked to "make total ignore negative prices", the entire response is the diff in diff -u format — 3 context lines each side, file headers, hunk header — followed by one line of why:

diff
--- a/src/cart.ts
+++ b/src/cart.ts
@@ -5,7 +5,7 @@ export function total(items: Item[]): number {
   return items.reduce((sum, item) => {
-    return sum + item.price;
+    return sum + Math.max(0, item.price);
   }, 0);
 }

Clamping each price at 0 prevents a refunded line item from reducing the cart total below the legitimate sum.


Benchmark

Scenario: .benchmarks/scenarios/show-me-the-code-001-diff-response.md · Run: 2026-08-31 · Log: .benchmarks/runs/2026-08-31/show-me-the-code-001-diff-response.json

ModelWithoutWithDelta
claude-opus-4-833%100%+67%
claude-sonnet-4-633%83%+50%
claude-haiku-4-517%83%+66%
PASS (run 2026-08-31). Large uniform gains; no regressions. Gate per .agents/skills/skill-optimizer/rules/release-gates.md.
del mismo repositorio

Más Skills

Todos los Skills
bsene
Comunidad

c4-diagram

Generates C4 model architecture diagrams using Structurizr DSL (primary) or Mermaid C4 (fallback). Use when: user asks to "draw a diagram", "create a C4 diagram", "show architecture as a diagram", "generate architecture diagram", "document the system". DO NOT USE for code explanation or walkthroughs (use explain-code), class/sequence/ER diagrams (C4 is system-architecture only), or when a diagram is incidental to a code change — only when a C4 diagram is the primary deliverable.

instalaciones
1
GitHub Stars
5
Actualizado
21 sept
bsene
Comunidad

clean-code

Use when writing new code, naming modules/files/functions/classes/variables, reviewing or refactoring code for readability, assessing/reducing complexity, deciding whether an abstraction belongs, or reviewing with CUPID. For behavior-preserving refactors within a function, class, or file, route to the refactoring/ sub-skill. Trigger on requests like "name this function", "is this a good variable name", "review this for clean code", "reduce complexity", "should I add a comment here", "should I abstract this", "review with CUPID", "code smell", "extract method", or "refactor this class". Covers human-scale design, naming, complexity budgets, comments, CUPID, and in-place refactoring. Pairs with language-specific skills (typescript, go, clojurescript) for syntax/idiom concerns.

instalaciones
1
GitHub Stars
5
Actualizado
21 sept
bsene
Comunidad

clojurescript

Write, review, debug, and configure ClojureScript code and projects. Use this whenever the user mentions ClojureScript, .cljs/.cljc files, shadow-cljs, figwheel, the CLJS compiler, JS interop from Clojure, Reagent/re-frame/Reagent-style UI code, or asks to convert JS/TS logic into ClojureScript. Also use it for questions about CLJS compiler options (:optimizations, :main, :npm-deps, :externs, etc.), consuming JS/npm libraries from CLJS, source maps, Google Closure Library usage, or the newer ^:async/await function support. Also trigger for CLJS recursion/stack-overflow/trampoline questions. Trigger even if the user just pastes CLJS code with an error and asks "what's wrong here" or asks to set up a new CLJS project. Do NOT use for nbb (babashka/nbb) scripts, nbb.edn projects, or anything meant to run via nbb script.cljs/npx nbb — those have a different (SCI-interpreted, no-Closure-Compiler) language surface; those are out of scope for this skill — consult nbb's own documentation.

instalaciones
1
GitHub Stars
5
Actualizado
21 sept
bsene
Comunidad

communication

Analyze a real communication artifact (Slack/Teams message, email, meeting transcript, pitch or presentation draft, CV, or resume) and coach it sharper using seven rhetoric + structure techniques: ethos/logos/pathos, reframing tough questions, centering the other person, the Pyramid Principle, pattern interrupt, making ideas feel safe, and the cognitive-load through-line. Diagnose what works, what's missing, then rewrite. TRIGGER when: user wants to improve communication, "review my email/Slack/CV", "analyze this transcript", prep for a meeting/pitch/presentation, "how do I say this", be more persuasive/assertive, handle a tough question, talk to execs, "is this too long-winded". Also trigger for author style presets under references/authors/: DHH (blunt/direct), Uncle Bob (defend a quality/testing standard), Jessitron (reflective systems-thinking essay), Martin Fowler (measured mixed-feelings stance). DO NOT USE for raw text generation with no analysis, marketing/copywriting, translation, or code/docs.

instalaciones
1
GitHub Stars
5
Actualizado
21 sept