Menu
Skills in this repository
SkillsMP has collected 176 skills from praxstack/ai-visual-code-review. Open a skill to review its source and details.
praxstack/ai-visual-code-reviewShowing 40 of 176 collected skills.
Builds, deploys, manages, debugs, configures, and optimizes serverless applications on AWS using Lambda, API Gateway, Step Functions, EventBridge, and SAM/CDK. Covers cold starts, CORS debugging, event source mappings, troubleshooting, concurrency, SnapStart,…
Authors and edits AWS Step Functions state machines: writes Amazon States Language (ASL) in JSONata, and chooses and structures state types (Task, Choice, Map, Parallel, Pass, Wait, Succeed, Fail). Covers ASL syntax, JSONata data transformation and variables,…
Helps migrate self-managed Apache Kafka workloads to Amazon MSK Express. Inventories the source cluster (from IaC files, Kafka CLI output, or manual input), assesses MSK Express compatibility across topology, Kafka version, configs, auth, and quotas, produces…
Provisions, connects, migrates, and operates Amazon RDS for Db2. Applies when provisioning with IBM customer and site IDs (License Manager, BYOL, GovCloud), connecting over TLS, fixing SQL30082N after Secrets Manager rotation, migration from Db2 LUW (Linux,…
Babysits an open GitHub PR until merge-ready. Use when asked to watch a PR over time — not for one-shot comment resolution or one CI failure. GitHub (incl. Enterprise) only.
Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm, scope what to build, or needs collaborative product framing before planning. Also use when they must scope work in territory they do not…
Structured code review for bugs, regressions, tests, and standards. Use before PRs or when asked to review code. Use when the user asks to apply this review's findings locally. Not for resolving feedback already left on a PR; that is ce-resolve-pr-feedback.
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
Refresh the repo's captured learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless the learnings store is explicit.
Document a recently solved problem as a durable repo learning. Use when capturing a learning after work.
Diagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing behavior.
Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.
Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.
Give a decisive, project-grounded point of view: a graded verdict on an external-adoption question, a holistic take on a document, or a position on a supplied approach set. Use for a solo POV. Use when asked to consult other models, reconcile their opinions,…
Resolve PR review feedback. Use when addressing feedback already left on a PR. Not for reviewing the code before feedback exists; that is ce-code-review.
Check Compound Engineering health and repo-local config.
Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without…
Run the full autonomous shipping pipeline end-to-end, hands-off with no check-ins. Use only when the user explicitly asks to build or ship something autonomously all the way to an open PR, or invokes lfg directly — it pushes and opens a PR without stopping.…
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. (gstack)
Post-deploy canary monitoring. (gstack)
OpenAI Codex CLI wrapper — three modes. (gstack)
Restore working context saved earlier by /context-save. (gstack)
Save working context. (gstack)
Chief Security Officer mode. (gstack)
Design consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview... (gstack)
Design finalization: generates production-quality Pretext-native HTML/CSS. (gstack)
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)
Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. (gstack)
Live developer experience audit. (gstack)
Generate missing documentation from scratch for a feature, module, or entire project. (gstack)
Post-ship documentation update. (gstack)
Code quality dashboard. (gstack)
Systematic debugging with root cause investigation. (gstack)
Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)
Visual design audit for iOS apps on real hardware. (gstack)
Autonomous iOS bug fixer. (gstack)
Live-device iOS QA for SwiftUI apps. (gstack)
Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)
Land and deploy workflow. (gstack)
Read-only queue dashboard for workspace-aware ship. (gstack)