'release' 검색 결과

Drives OBS Studio through its WebSocket, read-only by default, and turns recordings into clips, VOD cuts and chapters with FFmpeg. Trigger to audit an OBS setup; when a stream drops frames or lags; to switch a scene, mark a moment or save the replay buffer; to cut clips, burn in captions, normalize loudness or write chapters; when OBS shares a GPU; or say obsrunner (audit, check, set, mark, post, sheet, status, hold, release, refresh). Live work needs the user-installed obsws-python package. Never goes live, uploads or moderates chat. Caption files are whisperrunner's; thumbnails comfyrunner's; titles commscribe's; analytics duckrunner's.

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

Finds what changed in Claude — docs, release notes, changelogs, GitHub and community posts on Claude Code, claude.ai, Cowork, the API and models — and turns each change into adopt rows for your setup, plus a fit card for a new model or feature and a monthly bench of your skills against public skill and plugin repos (build, adopt or skip). Trigger on what changed since a date or version, a weekly sweep, features worth adopting, a feature that broke unannounced, a stale model table, what a new model or feature is good for, or how your skills compare with popular or little-known skill and plugin repos; or say scoutwright (sweep, since, watch, adopt, fit, bench, sources, refresh). Outside research is researchscribe's; applying a row, skillwright's; config, rigwright's; schedules, agentwright's; tier picks, promptwright's.

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

Use when GitHub may have shipped a GraphQL schema update affecting timeline event unions (PullRequestTimelineItems / IssueTimelineItems), when the gh-timeline dispatcher fallback is hitting more than expected, before a gh-timeline release, or when the user requests phrases like "verify timeline coverage", "audit gh-timeline schema", "check for new timeline events", "GitHub schema changed". Walks through schema diff → patch → test update → live verification → optional fixture refresh, marking each spot where a human decision is required.

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

Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.

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

Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.

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

Generate user-facing App Store release notes from git history since the last tag.

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

Scan recent git commits for changes that affect user-facing behavior, then draft or update the corresponding documentation pages. Use when docs have fallen behind code changes, after a batch of features lands, or when preparing a release. Trigger keywords - update docs, draft docs, docs from commits, sync docs, catch up docs, doc debt, docs behind, docs drift.

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

Runs the end-of-day maintainer handoff for NemoClaw. Checks version target progress, bumps stragglers to the next patch version, generates a QA handoff summary, and cuts the release tag. Use at the end of the workday. Trigger keywords - evening, end of day, EOD, wrap up, ship it, cut tag, handoff, done for the day.

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

Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Trigger keywords - nemoclaw ecosystem, openclaw openshell, nemoclaw vs openshell, sandboxed openclaw, how nemoclaw works, nemoclaw sandbox lifecycle blueprint, nemoclaw overview, openclaw always-on assistants, nvidia openshell, nvidia nemotron, nemoclaw release notes, nemoclaw changelog.

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

Tracks competitors weekly across 6 signals: pricing page diffs, homepage positioning changes, blog/RSS posts, job postings (hiring as strategy signal), GitHub star velocity and releases, and daily critical-change alerts for pricing or funding keywords. Delivers a structured digest to Slack, Telegram, WhatsApp, or Discord every Monday. Fires same-day alerts for critical changes. Use when asked to "add competitor", "track competitor", "competitor digest", "what changed at [company]", "competitor report", "monitor [company]", "who is [company] hiring", "did [company] change pricing".

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

Audit wiki health — "wiki health check", "audit the wiki", "find contradictions", weekly pass, before a major content release. Catches contradictions, stale pages, orphans, duplicate concepts and broken links.

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

Review and verify unverified wiki pages — "review unverified pages", "verify wiki content", verification pass, after a major ingest cycle, before content release. The gate that turns AI-generated knowledge into trusted knowledge.

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

GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.

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

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

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

Migration and code evolution instructions generator for GitHub Copilot. Analyzes differences between two project versions (branches, commits, or releases) to create precise instructions allowing Copilot to maintain consistency during technology migrations, major refactoring, or framework version upgrades.

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

Comprehensive skill for working with Azure DevOps REST API across all services including Boards (work items, queries, backlogs), Repos (Git, pull requests, commits), Pipelines (builds, releases, deployments), Test Plans, Artifacts, organizations, projects, security, extensions, and more. Use when implementing Azure DevOps integrations, automating DevOps workflows, or building applications that interact with Azure DevOps services.

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

Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.

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

Audit and remediate dependency/package vulnerabilities across .NET backend, frontend (npm/pnpm/yarn), and Rust projects with severity-based quality gates. Use when the user asks for SCA checks, dependency hardening, or release security gates before build/package.

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

Audit and remediate dependency/package vulnerabilities across .NET backend, frontend (npm/pnpm/yarn), and Rust projects with severity-based quality gates. Use when the user asks for SCA checks, dependency hardening, or release security gates.

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

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is reached.

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

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is ready.

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

Build and harden high-performance APIs with strong security controls, endpoint budgets, rate limiting, and resilience patterns. Use when tasks involve API latency/throughput tuning, abuse resistance, authz hardening, or API release gates.

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

Mandatory final risk-focused review for any repository change. Checks security, architecture boundaries, test coverage, and release readiness before closeout.

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

Orchestrate complete lifecycle work for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM as a Cloud Service, from design and implementation through validation, release readiness, and incident troubleshooting.

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