Results for “prettier”

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.

Price-to-win lens using GSA CALC+, BLS OEWS, and incumbent USASpending award patterns for a pursuit. Use when user asks for realism checks or competitive pricing posture before proposal — draft skill, not production-verified.

Use when designing a near-black premium UI with subtle ordered-dither texture and a thin accent-colored laser atmosphere. Prefer this over mengto-dither-background when dither pairs with laser accents; prefer over mengto-blue-laser-clean-glass-layout when ordered dither texture is the surface cue, not frosted glass dashboards.

Creates a GitHub pull request with an auto-generated summary, running mandatory pre-commit and code-quality review gates, plus optional deep-review subagents, and posts findings into the PR body.

CHEETAH v2.0 — HYPE Predator. SM commitment as primary signal. Top performer at +7.6%. All fleet fixes applied.

Create, refresh, and rewrite PR titles and descriptions following Sentry conventions, focusing on reviewer-facing content that describes the full branch diff.

Selects Jetson-compatible containers, vLLM runtime images, and Jetson AI Lab PyPI indexes based on Orin SM 8.7 vs Thor SM 11.0 and JetPack version.

Simple headless Puppeteer browser for rendering JavaScript-heavy pages and extracting clean text content. Use when user needs to read a web page that requires JS rendering. Command: openclaw browser read <url>. Requires: node, puppeteer.

Create pull requests with structured descriptions based on committed branch diffs, following Sentry's engineering practices.

Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract to build systems that are easy to change, understand, and trust.

Open a GitHub PR with a tight body — why this change, what'll surprise the reviewer, how we know it's correct — or add a pull_request_template to a repo. Use when asked to open, create, or draft a pull request, compose or regenerate a PR description, or scaffold a repo's PR template. Composes the Summary/Gotchas/Verification structure and detects an existing template first.

Master orchestrator to resolve a PR by diagnosing state and delegating to specialized skills.

Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization.

Turn a plain-text README into a visually rich showcase with a theme-aware hero image, a feature tour grid, an optional animated guided-tour GIF, and updated tech badges. Use when asked to "enhance README", "make README prettier", "add screenshots to README", "showcase the app in README", "design the README", "add hero.

Self-contained code review checklist — formatting, type safety, duplication, readable conditions, logic-out-of-UI, test coverage, comment quality. Adapts to whatever tooling the project actually has (skips Prettier/TypeScript/test-runner checks if unconfigured). Use before merging, after completing a feature, or any time you want a second pass on code quality. In Claude Code, prefer the official `code-review` skill or `pr-review-toolkit`/`feature-dev` code-reviewer agents instead — both are real, installed, and go deeper than this checklist. This copy exists for Codex/Cursor portability, where those agents aren't available.