All authors
Claude Skills by johnqtcg
github.com/johnqtcg61 skills0 installs126 views
- ISSUE TEMPLATE<!-- The concrete task a user brings to their AI coding assistant that this skill would handle. -->Votes: 0GitHub stars: 30
- Answers**Direct answer: No.** govulncheck does not emit a CVSS score for any vulnerability it reports, in its default text output, its JSON schema, or (per its own documentation) SARIF/VEX output. It identifies vulnerabilities by a Go-assigned `GO-YYYY-NNNNN` ID and expresses risk via a reachability classification (symbol called / package imported / module required) instead of a CVSS number. See Key Findings below for the sourced evidence.Votes: 0GitHub stars: 30
- Answers**No.** `govulncheck` does not emit a CVSS score (or any other severity label — LOW/MEDIUM/HIGH/CRITICAL) for the vulnerabilities it reports, in either its human-readable text output or its structured `-json` / `-format json` output. This is a deliberate design decision by the Go Security team, not a missing feature.Votes: 0GitHub stars: 30
- Answers- Normalized question: PostgreSQL logical replication vs Debezium for streaming order-database changes into Kafka: which should we use, and what are the tradeoffs? - Research kind: `web` - Depth mode: `deep` - Evidence chain requirements: typed evidence; extracted excerpts for web claims; repository evidence IDs for codebase claimsVotes: 0GitHub stars: 30
- Answers**Prepared for:** tech lead review **Question:** how do we stream row-level changes out of the orders database into Kafka — using PostgreSQL's native logical replication directly, or Debezium (Kafka Connect based CDC)? **Method note:** compiled from vendor/official documentation and independent technical sources via live web search on 2026-09-08. Every claim below is footnoted to its source; see the Sources list at the end for full URLs. I have not run these two setups myself against your ord...Votes: 0GitHub stars: 30
- Answers- Normalized question: I have two different pages in the MySQL 8.0 manual that seem to say opposite things about whether an INSTANT ALGORITHM DDL takes a metadata lock for the whole operation or only briefly. Work out which is right and show your reasoning. This is going into a migration runbook that the DBA team will follow during a maintenance window. - Research kind: `web` - Depth mode: `deep` - Evidence chain requirements: typed evidence; extracted excerpts for web claims; repository evidencVotes: 0GitHub stars: 30
- Answers**Both statements are true; they are not actually in conflict once you separate lock *mode* (shared vs. exclusive) from lock *duration*.**Votes: 0GitHub stars: 30
- Answers- Normalized question: What percentage of Fortune 500 companies run Apache Kafka in production as of 2026? - Research kind: `web` - Depth mode: `standard` - Evidence chain requirements: typed evidence; extracted excerpts for web claims; repository evidence IDs for codebase claimsVotes: 0GitHub stars: 30
- Answers**There is no reliable, independently verified statistic for "the percentage of Fortune 500 companies running Apache Kafka in production as of 2026."** I checked primary sources directly (Apache's own site, Confluent's marketing pages, Confluent's 2021 SEC S-1 filing, IBM's Kafka page) rather than relying on secondary summaries, and every number in circulation traces back to unaudited vendor marketing claims — none dated 2026, none with a disclosed methodology, and they don't even agree on whichVotes: 0GitHub stars: 30
- Api DesignREST API contract designer and reviewer. ALWAYS use when designing new endpoints, reviewing existing API contracts, planning API versioning, or standardizing error models. Covers resource modeling (URL/naming), HTTP method semantics, status code selection, error model consistency, pagination/filtering/sorting, idempotency keys, concurrency control (ETag/If-Match), object-level authorization (IDOR prevention), rate limiting, backward compatibility assessment, and OpenAPI-ready output. Use even...Votes: 0GitHub stars: 30
- Api Integration TestCreate, maintain, and run gated Go integration tests for internal APIs and service-to-service clients (HTTP/gRPC). Use for endpoint verification, contract checks with real runtime config, opt-in execution, timeout/retry safety, and integration failure triage in Go services.Votes: 0GitHub stars: 30
- Constructive ThinkingCompress chaotic information into a leader-ready structure before output. ALWAYS use when the user is preparing to brief a senior leader, present a technical proposal, write a one-pager, or otherwise turn scattered facts and feelings into Frame → Crux → Nodes → Tilt + Reasoning that fits in 3–5 minutes of reading. Trigger phrases include "向领导汇报", "做技术方案 presentation", "整理思路", "report up", "brief the boss", "summarize for leadership", "executive briefing", "one-pager". NOT for writing the fina...Votes: 0GitHub stars: 30
- Create PrCreate evidence-backed pull requests to the GitHub main branch with strict preflight, quality, and security gates. Use when users ask to create/submit/open/update a PR to main (including private repos), decide draft vs ready state, and provide reviewer-ready context for team review.Votes: 0GitHub stars: 30
- Deep ResearchSource-verified research: fact-check a claim, settle documents that contradict each other, compare options for a decision someone will challenge, or trace how code in a repository actually behaves — citing the exact page excerpt, file line or test that proves each point. Use when the answer will be questioned or being confidently wrong is costly — a board memo, design doc, audit, vendor contract, PR dispute — and for "is it true that…", "verify / fact-check this", "the docs disagree", "where ...Votes: 0GitHub stars: 30
- E2e TestDesign, maintain, and execute reliable end-to-end tests for critical user journeys with Agent Browser as first choice for exploration and Playwright as the preferred code path for suites and CI. Use for E2E strategy, journey coverage, flaky test triage, artifact collection, CI gating, regression prevention, and browser automation tasks.Votes: 0GitHub stars: 30
- Fuzzing TestGenerate Go fuzz tests (Go 1.18+ testing.F) for specified code when users ask for fuzzing/模糊测试/fuzz test generation, parser robustness, round-trip, or differential fuzzing. Always run an applicability gate first; if the target is not suitable, explain concrete reasons and stop without writing fuzz test code.Votes: 0GitHub stars: 30
- Git CommitSafely create a git commit by validating repository state, staging intended changes, scanning for secrets/conflicts, generating a Conventional Commits message (repository convention first, else an English Angular default) from the staged diff, and committing without amend.Votes: 0GitHub stars: 30
- Go BenchmarkGo performance benchmarking and pprof profiling specialist. ALWAYS use when writing benchmark functions (testing.B), generating or reading pprof profiles, interpreting flame graphs, finding memory allocation hotspots, comparing implementations with benchstat, or measuring ns/op / B/op / allocs/op. In Go code contexts, also trigger when the user says "it's slow", "too many allocations", "find the bottleneck", or "profile this Go code".Votes: 0GitHub stars: 30
- Go Ci WorkflowUse when creating or refactoring GitHub Actions CI workflows for Go repositories. Covers repository-shape detection, Make-driven delegation with formal fallbacks, Go setup, caching, tool pinning, permissions, reusable workflows, and quality gate design.Votes: 0GitHub stars: 30
- Go Code ReviewerReview Go code with a defect-first approach using repository policy (constitution.md first, then AGENTS.md fallback). Use for code review, PR review, quality checks, risk analysis, and regression detection.Votes: 0GitHub stars: 30
- Go Concurrency ReviewReview Go code for concurrency safety and goroutine lifecycle issues including race conditions, deadlocks, goroutine leaks, mutex misuse, and context propagation. Trigger when code contains go func, channels, sync primitives, WaitGroup, errgroup, or goroutine lifecycle management. Use for concurrency-focused review of Go projects.Votes: 0GitHub stars: 30
- Go Dependency AuditGo dependency audit specialist for CVE scanning (govulncheck), license risk triage, outdated dependency detection, upgrade impact analysis, and supply chain security. ALWAYS use when auditing go.mod dependencies, running govulncheck, checking license compatibility, planning dependency upgrades, or investigating supply chain risks in Go projects. Read-only by default — emits a remediation plan instead of mutating go.mod/go.sum. Complements security-review (code-level) with module-level supply ...Votes: 0GitHub stars: 30
- Go Error ReviewReview Go code for error handling correctness, nil safety, and failure-path integrity including ignored errors, missing wrapping, panic misuse, SQL/HTTP resource lifecycle, and transaction patterns. Trigger when code contains error returns, panic calls, sql.Rows, transactions, HTTP client/server code, or nil-sensitive pointer operations. Use for error-handling and correctness-focused review.Votes: 0GitHub stars: 30
- Go Logic ReviewReview Go code for business logic correctness, boundary conditions, off-by-one errors, state management, data flow integrity, and return value contracts. Trigger on any Go code change that modifies behavior, conditional logic, state transitions, or data processing. Use for logic-correctness focused review.Votes: 0GitHub stars: 30
- Go Makefile WriterCanonical skill for Go Makefiles. Create/refactor root Makefiles for Go repositories with standardized build/test/lint/run targets, self-documenting help output, predictable artifacts, and maintainable target naming.Votes: 0GitHub stars: 30
- Go Observability ReviewReview Go code for observability gaps: missing structured logging, broken trace context propagation, Prometheus cardinality explosions, span lifecycle errors, and sensitive fields in logs. Dispatched by go-review-lead as a vertical reviewer. Also trigger directly when the user says "review my logging", "check my tracing", "observability review", or "are my metrics correct".Votes: 0GitHub stars: 30
- Go Performance ReviewReview Go code for performance issues including slice/map pre-allocation, string concatenation, N+1 queries, connection pool configuration, sync.Pool, memory alignment, lock scope, buffered I/O, and HTTP transport tuning. Trigger when code contains make(), loops, database queries, string building, sync primitives, HTTP clients, or hot-path operations. Use for performance-focused review.Votes: 0GitHub stars: 30
- Go Quality ReviewReview Go code for code quality, style, and modern Go practices including function length, nesting depth, naming, mutable globals, interface design, receiver consistency, modern Go idioms (slog, generics, typed atomics), and static analysis. Trigger when reviewing Go code structure, readability, or maintainability. Also runs golangci-lint for automated style checks.Votes: 0GitHub stars: 30
- Go Review LeadOrchestrate a comprehensive Go code review by triaging code changes, dispatching vertical review skills (security, concurrency, error, logic, performance, quality, test, observability) as parallel agents, then consolidating results into a unified report. Use for full Go PR review or comprehensive code review. Replaces the monolithic go-code-reviewer with focused parallel analysis.Votes: 0GitHub stars: 30
- Go Security ReviewReview Go code for security vulnerabilities including OWASP Top 10, injection, auth/authz, crypto, secrets, SSRF, XSS, and input validation. Trigger when code involves SQL, user input, authentication, HTTP handlers, TLS, crypto, secrets, or file path operations. Use for security-focused code review of Go projects.Votes: 0GitHub stars: 30
- Go Test ReviewReview Go test code for quality including table-driven tests, t.Helper usage, assertion completeness, boundary cases, benchmarks, fuzz tests, and coverage targets. Trigger when PR contains _test.go files, test helpers, httptest usage, testing.B, testing.F, or testdata directories. Use for test-quality focused review.Votes: 0GitHub stars: 30
- Google SearchUse when the user wants help finding information through Google or Google-style web search and expects more than raw links. Handle current facts, public-information lookups, official documents, tutorials, reports, tools, materials, or source discovery by classifying the search goal, generating precise queries, executing search, ranking sources, cross-checking key claims, and returning a concise conclusion plus reusable search strings. Also use for programmer-specific searches (error debugging...Votes: 0GitHub stars: 30
- Incident PostmortemIncident post-mortem specialist for writing blameless post-mortems, extracting timelines from logs/events, conducting root cause analysis (5-Why, fishbone), classifying severity, and generating tracked action items. ALWAYS use when writing a post-mortem, reviewing an incident, extracting a timeline, performing root cause analysis, or converting incident data into organizational knowledge. Complements systematic-debugging (finds the cause) with structured documentation that prevents recurrence.Votes: 0GitHub stars: 30
- Kafka Event Driven DesignKafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition (Avro/Protobuf/JSON Schema), Schema Registry compatibility modes, idempotent consumption, dead letter queues, exactly-once semantics, backpressure, and consumer lag. Use even fo...Votes: 0GitHub stars: 30
- Load TestPerformance load testing specialist for writing k6/vegeta/wrk scripts, defining SLOs, modeling scenarios (spike/soak/stress/breakpoint), analyzing results, and identifying bottlenecks. ALWAYS use when writing load test scripts, reviewing test results, designing test scenarios, setting performance SLOs, or diagnosing latency and throughput issues at the service level. Complements go-benchmark (micro-level function profiling) with macro-level end-to-end service testing. Use proactively for any ...Votes: 0GitHub stars: 30
- Local TranscriptTranscribe a specified local video or audio file into cleaned final `.txt`, `.pdf`, or `.docx` transcripts using speech recognition with Apple Silicon GPU acceleration and optional LLM-based proofreading. Use when the user wants text extracted from a local media file path such as `.mp4`, `.mov`, `.mkv`, `.webm`, `.mp3`, `.m4a`, or `.wav`, and the output language should follow the spoken language in the media automatically. Prefer this skill for local-file transcription workflows that should p...Votes: 0GitHub stars: 30
- Log AnalyzerSenior-SRE log analysis specialist. Use when investigating incidents from logs, triaging error spikes, extracting timelines, correlating distributed traces, or separating signal from noise across plain-text, JSON (slog/zap), syslog, journald, container, and Kubernetes logs. ALWAYS use when the user asks to "analyze logs", "find the error", "what went wrong", "investigate this outage", "correlate request_id/trace_id", "look at the log file", or hands over log dumps / aggregator queries / kubec...Votes: 0GitHub stars: 30
- Mongo MigrationMongoDB schema migration safety reviewer and migration script generator. ALWAYS use when writing, reviewing, or planning MongoDB schema changes — field additions/removals, index builds, schema validator changes, document type migrations, shard key modifications, or any bulk update touching production collections. Covers index build lock behavior (replicated default vs the rolling exception), additive schema evolution, batched backfills, write concern tuning during migration, reshardCollection...Votes: 0GitHub stars: 30
- Monitoring AlertingMonitoring and alerting design reviewer for production backend services. ALWAYS use when writing Prometheus alerting rules, designing Grafana dashboards, defining SLI/SLO, configuring alert routing (PagerDuty/OpsGenie/Slack), or reviewing existing monitoring setups. Covers SLI/SLO definition, alert rule quality (sensitivity/specificity tradeoff), burn-rate alerting, alert fatigue prevention, dashboard design principles, label cardinality management, and on-call routing configuration. Use even...Votes: 0GitHub stars: 30
- Mysql MigrationMySQL schema migration safety reviewer and DDL generator. ALWAYS use when writing, reviewing, or planning MySQL schema changes — ALTER TABLE, CREATE/DROP INDEX, column type changes, charset conversions, data backfills, or any DDL touching production tables. Covers online DDL algorithm selection (INSTANT/INPLACE/COPY), lock-safety analysis, large-table migration with gh-ost/pt-osc, phased rollout design, replication-safe DDL, backward compatibility, and rollback planning. Use even for "simple"...Votes: 0GitHub stars: 30
- Oceanbase Table DesignOceanBase distributed table design and modeling expert. Use this skill when the user: - asks to design tables, schema, or DDL in OceanBase - describes a workload and wants optimal schema design - asks about partitioning, indexing, table groups, columnstore, or avoiding distributed transactions in OceanBase - wants to review or optimize an existing OceanBase schema Do NOT use this skill for: - generic SQL questions unrelated to OceanBase - simple syntax lookups - non-database topicsVotes: 0GitHub stars: 30
- Oracle MigrationOracle Database schema migration safety reviewer and DDL generator. ALWAYS use when writing, reviewing, or planning Oracle schema changes — ALTER TABLE, CREATE/DROP INDEX, column type changes, constraint additions, partition DDL, or any DDL touching production tables. Covers DDL auto-commit implications, DDL_LOCK_TIMEOUT, DBMS_REDEFINITION for online table restructuring, ENABLE NOVALIDATE constraint patterns, global index impact from partition DDL, CTAS-based migration, ROWID-range batching, ...Votes: 0GitHub stars: 30
- Pg MigrationPostgreSQL schema migration safety reviewer and DDL generator. ALWAYS use when writing, reviewing, or planning PostgreSQL schema changes — ALTER TABLE, CREATE/DROP INDEX, column type changes, constraint additions, RLS policy changes, or any DDL touching production tables. Covers lock-level analysis, CREATE INDEX CONCURRENTLY, NOT VALID constraint patterns, transactional DDL rollback, expand-contract for table rewrites, pg_repack for online reorganisation, phased rollout design, and backward c...Votes: 0GitHub stars: 30
- Readme GeneratorGenerate or refactor project README.md files using repository evidence. Use when the user asks to create/rewrite/standardize README, improve documentation structure, or produce maintainable README templates for different project types (service/library/CLI/monorepo).Votes: 0GitHub stars: 30
- Redis Cache StrategyRedis caching strategy designer and reviewer. ALWAYS use when designing, reviewing, or troubleshooting Redis caching layers — cache pattern selection (cache-aside, write-through, write-behind), TTL strategy, cache stampede/penetration/avalanche prevention, hot key handling, cache-DB consistency, distributed locking, key naming, and degradation design. Use even for "just add a cache" requests — cache invalidation is one of the two hard problems in computer science, and a naive implementation c...Votes: 0GitHub stars: 30
- Security ReviewExploitability-first standalone security review of code changes, diffs, PRs, or services. Use when asked for a security review, security audit, vulnerability assessment, or pre-merge security check (安全审查/安全评审/漏洞排查) — covers auth, input, secrets, API, data, concurrency, container, third-party, and dependency risk across Go, Node.js/TypeScript, Java, and Python, with mandatory evidence, false-positive suppression, scope-based depth (Lite/Standard/Deep), and CWE/OWASP-mapped machine-readable out...Votes: 0GitHub stars: 30
- Stock Analysis LeadOrchestrate a US-stock investment analysis — classify sector archetype, fetch SEC filings, dispatch a tiered fan-out of six vertical equity-research agents (business model, earnings quality, balance sheet, management, industry, peer comparison) over a validated JSON findings contract, then synthesize a buy/hold/sell verdict with Bull/Base/Bear target ranges using sector-aware thresholds and an auditable probability-assignment procedure. Each verdict can persist to an opt-in JSON-Lines log so ...Votes: 0GitHub stars: 30
- Stock Balance Sheet ReviewReview a US-listed company's balance sheet health for an equity-research workup. Covers net-debt/EBITDA leverage, current ratio, cash runway, goodwill concentration and impairment history, DSO trend, inventory days, off-balance-sheet items (operating leases, contingent liabilities), and pension underfunding. Trigger when analyzing financial-statement risk at L4 of the seven-layer X-ray framework, or when assessing whether the company can survive a downturn. Dispatched by stock-analysis-lead.Votes: 0GitHub stars: 30
- Stock Business ReviewReview a US-listed company's business model and revenue structure for an equity-research workup. Covers product/service mix, customer concentration, geographic exposure, industry position, revenue-growth decomposition (organic vs acquired vs price vs volume), and information-tier discipline (which numbers are facts vs management narrative). Trigger when analyzing a single US ticker's business fundamentals, when reading 10-K Item 1 "Business" and Item 1A "Risk Factors", or when the orchestrato...Votes: 0GitHub stars: 30
- Stock Earnings Quality ReviewReview a US-listed company's earnings quality, cash-flow integrity, and operating leverage for an equity-research workup. Covers operating cash flow vs net income drift, free cash flow trajectory, capex character (maintenance vs expansion), equity issuance / shareholder-return yield, revenue-quality signals (receivables vs revenue growth, channel stuffing), gross-margin level and trend, operating leverage, and three-cost-rate hygiene (S&M, R&D, G&A). SaaS-specific metrics — ARR/NRR/GRR/CAC pa...Votes: 0GitHub stars: 30