'stash' 검색 결과

Upstash serverless Redis -- REST-based client, auto-serialization, pipelines, rate limiting, QStash, edge compatibility, global replication

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Entry point for documentation skills covering Upstash Search quick starts, core concepts, and TypeScript SDK usage. Use when a user asks how to get started, how indexing works, or how to use the TS client.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Lightweight guidance for using the Redis Rate Limit TypeScript SDK, including setup steps, basic usage, and pointers to advanced algorithm, features, pricing, and traffic‑protection docs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Separate a messy working tree with multiple tangled features into clean, focused PRs. Use when: (1) Working tree has uncommitted changes from multiple features mixed together, (2) Need to create a PR for just one feature from a mixed working tree, (3) "git stash pop" fails with "already exists, no checkout" for untracked files, (4) Pre-commit hooks block commits due to unrelated untracked files with errors, (5) Interface changes in one feature break consumer files from another feature in the same working tree. Covers git stash workflows, branch separation, conflict resolution, and pre-commit hook workarounds. Never stack PRs — always target main.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides quick-start guidance and a unified entry point for Vector features, SDK usage, and integrations. Use when users ask how to work with Vector, its TS SDK, features, or supported frameworks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create, track, switch, sync, and clean up Git branches. Covers naming conventions, safe branch switching with stash, upstream synchronization, and pruning merged branches. Use when starting work on a new feature or bug fix, switching between tasks on different branches, keeping a feature branch up to date with main, or cleaning up branches after merging pull requests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Edit the Prisma Next data contract — add models, fields, relations, indexes, enums, value objects (composite types), type aliases, namespaces (Postgres schemas), cross-contract foreign keys (cross-space FK), polymorphic types (`@@discriminator` / `@@base`), use extension namespaces (`pgvector.Vector(...)`, `cipherstash.EncryptedString(...)`), wire `prisma-next.config.ts` with `defineConfig` from the `@prisma-next/<target>/config` façade, and run `prisma-next contract emit`. Use for schema, models, fields, attributes, soft delete, paranoid, scopes, validations, callbacks, prisma schema, PSL, contract.prisma, contract.ts, contract.json, contract.d.ts, façade imports, `@prisma-next/postgres/config`, `@prisma-next/postgres/contract-builder`, `@prisma-next/postgres/control`, `@prisma-next/mongo/config`, `@prisma-next/mongo/contract-builder`, `extensions:`, `extensionPacks`, pgvector, cipherstash, postgis, paradedb, supabase, `@prisma-next/extension-supabase`, `@@control`, control policy, managed, tolerated, external, observed, PN-CLI-4002, PN-CLI-4003, PN-CLI-4011.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bring a Remotion branch up to date with the official main branch while preserving local changes and published history. Handle temporary change storage, merges, conflicts, validation, and a normal push when requested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Merge the latest main into a feature branch
• Fast-forward a local main branch
• Update a pull request branch while preserving published history

Retrieve current documentation and code examples from Context7 for libraries, frameworks, and developer tools. Use the results to answer questions about API syntax, configuration, installation, version migration, and library-specific problems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking current API syntax
• Finding setup and configuration examples
• Investigating version migration issues

Fetch current library documentation with the ctx7 CLI to check API usage while coding. The skill also guides Context7 MCP setup, which connects documentation access to Claude Code, Cursor, or OpenCode, and covers login and authentication options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fetch current documentation for a library
• Check API signatures while writing code
• Set up Context7 for an AI coding agent

Look up current library and framework documentation with Context7 to explain setup, configuration, and APIs. Retrieve relevant code examples, prefer official packages, and use documentation for a specified version when available.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding framework setup and configuration steps
• Looking up library API references
• Finding code examples for implementation

Find current documentation and code examples through the Context7 MCP server. Look up library setup, API usage, migration steps, and library-specific problems, using documentation for the requested version when available.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Looking up documentation for a specific version
• Finding library setup and configuration steps
• Finding examples for code that uses external libraries

Search current library documentation and code examples with Context7 CLI, a command-line tool. Find API usage and configuration guidance, select available version-specific documentation, and prioritize examples in the programming language you use.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking current API usage and configuration
• Finding documentation for a requested version
• Prioritizing code examples in a chosen language

Compare accessibility findings between two versions of a web page. Identify newly introduced and fixed issues, count existing findings, and report evidence and suggested fixes without editing application code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check accessibility before committing local changes
• Compare a page against a branch baseline
• Confirm which accessibility issues a change fixed

Prepare local iPolloWork changes for GitHub while staying on the current personal branch. Preserve edits, sync from main, report conflicts, commit and push changes, and create a pull request when requested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Sync a personal branch with main while preserving local edits
• Commit and push selected changes
• Create a pull request from the current branch to main

Collect product details from public shopping pages using a URL, keyword, or product identifier. Extract prices, stock status, images, ratings, and variants into structured data for product research, comparisons, and catalog collection.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing product prices and stock across shopping sites
• Finding product details by ASIN or barcode
• Collecting images and descriptions for a product catalog

Coordinate project or repository renames and moves across Git, tools, services, and machines. Preserve local work and history, update affected paths and references, and verify that the relevant workflows function at the new location.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Rename a repository and update its references
• Move a project while preserving local work
• Update service paths after a directory move

Structured logging extensions for Golang using samber/slog-**** packages — multi-handler pipelines (slog-multi), log sampling (slog-sampling), attribute formatting (slog-formatter), HTTP middleware (slog-fiber, slog-gin, slog-chi, slog-echo), and backend routing (slog-datadog, slog-sentry, slog-loki, slog-syslog, slog-logstash, slog-graylog...). Apply when using or adopting slog, or when the codebase already imports any github.com/samber/slog-* package.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working on multiple branches simultaneously, context switching without stashing, reviewing PRs while developing, testing in isolation, or comparing implementations across branches - provides git worktree commands and workflow patterns for parallel development with multiple working directories.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audits, preserves and recovers local Git state before cleanup: unpushed or wrong-branch commits, dirty worktrees, duplicate clones, stashes, dangling commits, squash-merge uncertainty. Use when the user fears lost work, wants to recover a commit, asks if a branch is actually merged, asks whether a branch, worktree or clone is safe to delete, or wants one clean main (误删分支 / 还有没有丢的东西). Not for GitHub PR operations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deploy and manage the ELK Stack (Elasticsearch, Logstash, Kibana) for log aggregation and analysis. Configure log pipelines, create visualizations, and implement log-based monitoring. Use when centralizing logs, implementing search functionality, or building log analytics platforms.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit a project's infrastructure and SaaS stack, then produce a cost report showing what the user currently pays and what they would save by consolidating onto Temps (self-hosted or Temps Cloud). Detects hosting platforms (Vercel, Netlify, Railway, Render, Heroku, Fly.io), analytics (PostHog, Plausible, Mixpanel, Amplitude, Fathom), error tracking (Sentry, Bugsnag, Rollbar, Honeybadger), session replay (LogRocket, FullStory, Hotjar, Highlight), uptime monitoring (Pingdom, UptimeRobot, Better Stack, Checkly), managed databases (Supabase, Neon, PlanetScale, MongoDB Atlas, Upstash, RDS), and transactional email (SendGrid, Postmark, Resend, Mailgun) from dependencies, config files, and env var names. Use when the user wants to: (1) Know how much they would save by switching to Temps, (2) Audit their SaaS/infrastructure spend, (3) Compare their current stack's cost against self-hosting, (4) Decide whether Temps is worth it, (5) Build a business case for consolidating tools. Triggers: "how much would I save", "temps savings", "cost comparison", "audit my stack", "am I overpaying", "saas spend", "calculate savings", "is temps cheaper".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement BullMQ job workflows in NestJS. Use when building queue processors, redis-throttler, Upstash limits, idle polling, stalled jobs, and retention policies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Enhanced git operations using lazygit, gh (GitHub CLI), and delta. Triggers on: stage changes, create PR, review PR, check issues, git diff, commit interactively, GitHub operations, rebase, stash, bisect.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.