Skill Claude CodeCodex
Review code architecture (SOLID, design patterns, package design, coupling, testability), Go best practices, and protobuf/API design using manual analysis and static analysis tools (gocyclo, staticcheck, buf). Use when the user asks for a code review, architecture review, Go review, protobuf review, SOLID review, or…
Skill Claude CodeCodex
Use when the user asks for a coverage review, test coverage analysis, coverage gap analysis, uncovered code review, or wants to know what new/changed Go code is missing tests. Runs go test -coverprofile against the resolved scope and reports uncovered functions in changed Go files, grouped by package, with severity…
Skill Claude CodeCodex
Review database usage for migration safety, query performance, connection/transaction management, and schema design. Covers PostgreSQL and MySQL. Runs squawk for PostgreSQL migration linting if available. Use when the user asks for a database review, SQL review, migration review, or schema review.
Skill Claude CodeCodex
Review documentation quality and sync with implementation across Go doc comments, proto comments, OpenAPI specs, markdown files, and example tests. Use when the user asks for a documentation review, doc audit, or wants to check that docs are in sync with code.
Skill Claude CodeCodex
Use when the user asks for an infrastructure review, IaC review, Terraform review, Kubernetes manifest review, Dockerfile review, Helm chart review, container review, gateway review (Envoy / Ingress / Gateway API), service mesh review (Linkerd / Istio), east-west traffic review, north-south traffic review, mesh…
Skill Claude CodeCodex
Use when the user asks for an observability review, telemetry review, logging review, metrics review, tracing review, OpenTelemetry review, OTel review, Prometheus review, "are we observable", logging audit, structured logging audit, trace coverage check, span coverage check, metrics cardinality review, or production…
Skill Claude CodeCodex
Use when the user explicitly asks for a performance review, benchmark review, profiling review, perf audit, pprof analysis, allocation review, latency regression check, hot-path review, throughput review, "is this fast enough", or "review perf". This skill is opt-in only — never run automatically as part of review-all…
Skill Claude CodeCodex
Use when the user asks to review the plan, sanity-check the plan, vet the plan, evaluate the plan, "is this plan ready", feasibility check on a plan, "review-plan PATH", or when another skill (like implement-plan) requests pre-flight plan evaluation before execution. Do NOT use when no plan file is in scope (the user…
Skill Claude CodeCodex
Perform a reliability review covering graceful shutdown, gRPC production patterns, stability patterns (timeouts, circuit breakers, bulkheads), and stability anti-patterns. Use when the user asks for a reliability review, production readiness assessment, stability analysis, or graceful shutdown audit.
Skill Claude CodeCodex
Perform a security review using STRIDE threat modeling, OWASP Top 10 analysis, and automated scanning (gosec, govulncheck). Use when the user asks for a security review, threat model, OWASP analysis, or security audit.
Skill Claude CodeCodex
Use when starting a session on a non-main branch, switching branches (git checkout, git switch), or when a hook prompts for session context update. Also invocable manually via /set-session-context.
Skill Claude CodeCodex
End-to-end shipping workflow. Formats, lints, tests, creates a changelog entry, commits with conventional commits, pushes, updates PR description, and suggests reviewers. Use when the user says "ship it", "commit and push", "fmt lint test commit push", or similar shipping commands.
Skill Claude CodeCodex
Use when writing or rewriting reader-facing technical text — documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, API guides, agent/system prompts — or when asked to "de-slop", "make this readable", "simplify this doc", "write for non-native readers", "apply STE", "Simplified…
Skill Claude CodeCodex
Use at the start of a workday or when the user says "start my day", "good morning", "/start-day", "morning", "what should I work on today", or wants a catch-up on what happened while they were away. Use when the user wants a short ranked list of what to tackle today.
Skill Claude CodeCodex
Run format, lint, build, and test verification before claiming work is complete. Detects the project toolchain (Taskfile, Makefile, or raw Go) and runs the appropriate commands. Use before committing, pushing, creating PRs, claiming a fix works, or any completion assertion.
Instructions file CodexOpenCode
Instructions for paultyng/ideate, covering agents.md, build features as mcp tools first, ui second, when to add ui and pattern.
Instructions file
Instructions for paultyng/ideate, covering claude.md — ideate, what this is, tech stack, project structure and build and run.
Skill Claude CodeCodex
Use when the user asks for a recap, status readout, or check-in across Ideate ideas (a logical work item; "session" is one facet of an idea, not the unit). Scope is the local Ideate workspace exposed by the ideate MCP. Use work-idea instead when the user wants to focus on or switch into a single idea.
Skill Claude CodeCodex
Use when the user wants to switch into, resume, or get caught up on a single Ideate idea. X may be referenced as an idea name, slug, session UUID, or fuzzy phrase. The unit of work is the idea — a session is one facet of it. Scope is the local Ideate workspace exposed by the ideate MCP.
Skill Claude CodeCodex
Drive cutting a new testagent release end-to-end: analyze the surface diff against the bump table in RELEASING.md, propose a version, draft three-bucket release notes, tag, watch CI, then publish curated notes.
Skill Claude CodeCodex
Use when refreshing a vendor's section of COMPATIBILITY.md after an upstream release, when task dumpcli: reports drift, when a contributor adds a flag or slash command not yet in the matrix, or for periodic coverage checks. Vendor is parsed from the trigger phrase. Triggers include "update claude compat", "research…
Skill Claude CodeCodex
Detect drift between testagent's upstream config corpus and vendor docs; surface net-new examples as a draft PR.
Instructions file CodexOpenCode
Instructions for paultyng/testagent, covering agents.md, what is testagent?, future phases, design conventions and layout.
Instructions file
Instructions for paultyng/testagent: Agent context lives in AGENTS.md. This file is a stub so Claude Code's per-project context loader picks it up.