个人作者
Oleksandr B.
Fluent in Backend-ese (microservices, distributed systems, you know the drill) Functional Programming Fanatic...
- Skills
- 127
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 0
Oleksandr B. 的 Skills 127
wiki-builder
Create and maintain a local Markdown research wiki (sources with provenance, compiled concept/source pages, index, maintenance log) driven by a per-wiki config. Use when the user wants to start a wiki or knowledge base, ingest sources into one, or query and update it; use wiki-page-writer for a single code deep-dive page.
refactoring-guru
Diagnose a named code smell and apply the smallest behavior-preserving refactoring, with verification before and after and an explicit stop condition. Use for structural refactors (extract, move, consolidate, change ownership), not for feature or bug work; for readability cleanup of recent changes use code-simplification.
legacy-seams
When changing untested legacy code, pin the observed results with characterization tests and open the smallest seam that substitutes only the blocking dependency, separate from any later logic change. Use when a clock, random source, I/O, global, or hidden constructor blocks a test or a safe edit. Use test-driven-development for a new behavior or a bug, refactoring-guru for one named structural refactor after the seam exists, and code-refactoring-tech-debt to choose which legacy to replace.
idea-refine
Refine a raw idea into a one-page brief (problem statement, recommended direction, assumptions to validate, MVP scope, not-doing list) through divergent then convergent thinking. Use when an idea is still vague or you want options and a stress test before committing; use interview-me when the goal itself is unclear and spec-driven-development once the direction is chosen.
code-review-and-quality
Review rubric and approval standard for any change before merge, including code written by you, another agent, or a human: five axes (correctness, readability, architecture, security, performance), change sizing, structural remedies, severity labels, and feedback technique. Use to judge whether a change is fit to merge; use code-review to run a PR or diff review end to end.
code-perfection
Smell and style gate for code you write or change. Bans known code smells (long method, large class, primitive obsession, long parameter list, data clumps, duplicate code, dead code, feature envy, shotgun surgery, flag arguments, message chains) and enforces behavior-preserving structure. On Scala files, enforces worxbend style. Use while implementing, reviewing a diff for smells, or when a smell or style violation is suspected. Routine construction stays with code-complete. SOLID and DRY stay with clean-code-guard. One named structural refactor stays with refactoring-guru.
code-complete
Construction discipline from Steve McConnell's Code Complete for implementing code: routine and class design, variable naming and data types, simple control flow, defensive checks at trust boundaries, and pseudocode-first design for complex routines. Use while writing or restructuring routines; for a post-edit quality pass use clean-code-guard.
andrej-karpathy
Working posture for coding agents on any code task: state assumptions and ask when unclear, write the minimum code the request needs, keep every changed line traceable to the request, and define verifiable success criteria before editing. Use as the default behavior for writing or changing code; for code-quality rules use clean-code-guard.
ponytail
Opt-in "lazy senior dev" session mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use only when the user explicitly asks for it: says "ponytail", "/ponytail", "be lazy", or "yagni mode", or asks to switch levels (lite, full, ultra). Not a default posture for ordinary coding tasks; andrej-karpathy covers that.
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with /i-have-adhd; stays on until "stop adhd mode".
security-best-practices
Language- and framework-specific secure-coding review using bundled per-framework references for Python (Django/Flask/FastAPI), JavaScript/TypeScript (Express/Next.js/React/Vue/jQuery) and Go. Use only when a security review or secure-by-default guidance is explicitly requested for one of those stacks; use security-and-hardening for framework-agnostic boundary hardening.
kubernetes-hardening
Harden Kubernetes clusters and workloads - Pod Security Admission, securityContext, service-account tokens, default-deny NetworkPolicy that keeps DNS, least-privilege RBAC, admission policy (ValidatingAdmissionPolicy/Kyverno), image digests and signature verification, secrets encryption, audit logging, CIS scanning and runtime detection. Use for a K8s security review or before exposing a cluster to production; use operating-kubernetes for day-to-day workload operations.
dependency-scanning
Scan third-party dependencies for known vulnerabilities and generate SBOMs - Snyk, Dependabot, OWASP Dependency-Check, npm/pip/go audit tools, CycloneDX/Syft - and gate CI on the results. Use when adding or tuning software-composition analysis; use dependency-upgrade to carry out the upgrades.
code-audit
Authorized white-box source-code security review - Semgrep/CodeQL/Bandit/gosec pattern hunting plus manual triage of each hit for reachability and exploitability, with fix verification. Use for a SAST review or PR/diff security audit of first-party code; use dependency-scanning for third-party CVEs.
audit-logging
Implement technical audit and security-event logging for systems and applications - event taxonomy, structured audit records, rsyslog/journald/Fluent Bit shipping, SIEM integration, retention by framework (SOC 2, HIPAA, PCI DSS) and tamper evidence. Use when a system must produce a trustworthy who-did-what trail; for general application logs, metrics and traces use observability-and-instrumentation.
api-security
Authorized security assessment of REST, GraphQL, WebSocket and SOAP APIs - discovery, authentication and authorization flaws (BOLA/IDOR/BFLA, JWT/OAuth), input validation, rate-limit and data-exposure testing, in a structured multi-phase workflow. Use for permitted testing of an API; use api-security-best-practices to build secure endpoints.
scala-stream-resource-scoping
Use when a Scala stream or effectful factory change moves where a resource, state or execution lane is acquired, owned, used or released - FS2 scope propagation across channels/prefetch/parEvalMap, FS2 foreign callback (Reactive Streams, Dispatcher, accept-loop) lanes and ownership, FS2 sink emission cardinality under drain/append/flatMap, and http4s stateful middleware factories (nonce, throttle) whose state must live at the acquisition boundary. Covers lifetime and ownership topology, not cancellation-outcome/finalizer semantics, HTTP protocol semantics or binary-compatibility law.
scala-runtime-diagnostics-hot-paths
Use when a Scala library change touches a diagnostic mode, failure-trace replay, a runtime diagnostic reader (fiber children/dumps), a per-step hot path (allocation, closures, macro/inline callsite bytecode) or a performance claim backed by a benchmark — covering Fastparse verbose failures/trace and ParsingRun cost, Cats Effect scheduler and packed-stack benchmarks, and ZIO fiber child observation. Unlike the effect-cancellation, stream-scoping, HTTP, compatibility-law and compiler-macro skills, its question is whether observation and optimization leave semantics unchanged and whether the evidence measures the path actually changed.