'release' 검색 결과

Write and publish changelogs — release notes that users read, versioning, and launch communication cadence.

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

Keep paperclip-docs in lockstep with the parent paperclipai/paperclip codebase. Detects code-surface changes (CLI, env vars, API routes, adapters, plugin SDK, schemas) and produces friendly-tutorial-voice doc updates. Two modes — `nightly` (tracks parent's default branch (currently `master`), targets the `nightly` branch, preview deploy) and `release` (on parent tag, merges nightly → main, tags, ships live). Trigger phrases: "sync docs", "update docs from paperclip", "/sync-docs", "check for paperclip changes", "is docs current".

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

Versioning and changelog management with @changesets/cli — adding changesets, version bumping, changelog generation, monorepo publishing, pre-release modes, and CI automation

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

Nx monorepo build system — workspace configuration, project graph, task pipelines, caching, generators, plugins, and release management

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

Update README, migration notes, changelogs, and operator-facing docs so shipped changes remain understandable after release.

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

Diagnose and fix failed Pharos GitHub Actions, adaptive PR checks, Cloudflare deploys, Pages releases, or scheduled automation. Use when a gate/run failed or the user asks to retrigger and iterate until clear.

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

Review pull requests, branch diffs, and uncommitted changes in this Flutter repository with a bug-finding mindset. Use when asked to review changes, review a PR, audit a diff, check standards, check compliance, or look for regressions, missing tests, release risks, or architecture mismatches.

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

Plan launch readiness, staged rollouts, production monitoring, rollback, communications, and post-launch validation. Use when the user asks for `/ship`, pre-launch checklists, release readiness, staged rollout plans, feature flags, deployment monitoring, or rollback planning.

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

Use when generating or editing an Nx version plan in .nx/version-plans/ — the bump type must always be `patch`, one package per file.

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

Use when hunting GitHub Actions cache poisoning vulnerabilities where an attacker can inject malicious content into the CI/CD cache and have it restored by a privileged downstream workflow. Trigger on: "cache poisoning", "actions/cache", "actions/setup-node", "node_modules cache", "GitHub Actions cache", "pnpm cache", "LRU eviction", "10GB limit", "Cacheract", "poisoned cache", "workflow cache attack", supply chain via CI cache, "ng-renovate", "cache stuffing", scheduled workflow cache restore, shared cache key, "hashFiles package.json", cross-workflow cache, PR workflow release workflow same key, "npm install prefer-offline", Cacheract, Gato-X, supply chain npm token.

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

Generate a prioritized review queue of registry skills and catalog items that need attention. Use this skill whenever someone asks: "what needs review?", "what's overdue for audit?", "where are the weak spots in the registry?", "what should I audit next?", "run a health check on the registry", "show me flagged skills", "find problems in the registry", "what skills need fixing?", or "triage the registry". This is the triage layer — it surfaces candidates ranked P0–P4 so that focused work (via /gaia-audit) targets the right things first. Run this before any audit pass. Also invoke proactively when a PR changes registry/named/ at scale, or before a release, to catch regressions early.

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

Close out a completed EPIC / sprint end-to-end: author a fact-verified meta-post announcing what shipped, archive the EPIC's handovers, snapshot orchestrator memory, gate the integration→main merge on CI-green + explicit human go, drive the version bump (merge-commit conventions that auto-sync classifies), and verify the release reached the registry/PyPI. Use when the user says "close out EPIC <n>", "wrap up the sprint", "ship the meta shift", "/epic-close", or asks to finalize an integration branch that is ready to merge to main. Generalizes the EPIC 1002 (Yggdrasil II) close-out. This skill orchestrates — it authors founder docs directly (superadmin) and delegates code/regen to workers; it NEVER merges to main without the human gate.

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

Audit and repair Gaia user-tree timelines so every skill's current rank is explained by a chain of Hero's Journey events. Trigger this skill when: a contributor's profile chart shows a stale rank (e.g. still shows 3★ after a demotion to 1★); someone asks to "trace what happened" to a skill's rank; `validate_timelines.py` is failing in CI; you need to backfill missing `demote` or `rank_up` events before cutting a release; a skill was reclassified or Star-Bar-reset and the user tree was never updated; or any time the registry node and user tree disagree on a skill's current level. Uses `scripts/trace_timeline.py` (dry-run + apply) and `scripts/validate_timelines.py` (CI gate). Do NOT hand-edit `timeline[]` arrays — the script synthesises properly labelled events with `previousValue`/`newValue` so the rank chart plots correctly.

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

Guidance for Tauri v2 global-shortcut plugin with conflict handling and release.

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

This skill provides guidance for maintaining documentation consistency with implementation in the vscode-sidebar-terminal project. Use this skill when creating or updating documentation, verifying documentation accuracy, preparing releases, or when the codebase has changed and documentation may need updates. This skill should be used proactively after implementing features or bug fixes.

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

Update the CHANGELOG.md with the description of the changes between the last released version and the new one

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

Guide users through `pulp upgrade` — discover new CLI releases, interpret migration notes for the hop they're performing, and apply breaking-change fixes (CMake macro renames, API surface changes, config file moves). Handles "upgrade pulp", "what's new", "migrate my project", "show breaking changes", and the `/upgrade` slash command. Pairs with the embedded migration index shipped in the CLI binary.

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

Maintain Pulp's macOS Intel (x86_64) portability lint and CI tiering — the PULP_INTEL_CANARY configure gate, intel_canary_lint.py + its allowlist, and the Tier 0-3 workflows (build.yml canary step, intel-portability.yml, nightly-intel.yml, release-cli.yml universal gate). Use when touching cross-arch build wiring, arch-gated SIMD, or Intel CI.

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

Use OpenClaw Manager (OCM) safely and correctly for OpenClaw environment lifecycle work, runtime installation/builds, release-shaped local builds, upgrades, migration/adoption, cloning existing user state, service supervision, gateway logs, dev worktrees, plugin testing, model/provider smoke tests, TUI/dashboard checks, cleanup, and concise reporting. Use whenever Codex is asked to use OCM, manage OpenClaw envs/runtimes/services, test OpenClaw with OCM, reproduce existing-user or new-user flows, or avoid breaking user state while working with OpenClaw.

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

Use when a task needs the judgment of an Endoscopy Technician — deciding whether to release or quarantine a scope after a failed leak test or minimum-effective-concentration (MEC) reading, handling a point-of-use treatment delay against the manufacturer's reprocessing window, triaging a borescope finding on a working channel, or troubleshooting equipment and passing accessories during a live GI procedure.

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

Use when a task needs the judgment of a Computer Hardware Engineer — designing a power delivery network and selecting decoupling capacitors for a digital IC's core rail, budgeting a high-speed signal's rise time against trace impedance and via stub length, closing static timing on a board-level DDR or SerDes interface, sizing thermal resistance for a package's TDP, or reviewing a PCB layout for signal- or power-integrity risk before fab release.

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

Use when a task needs the judgment of a Computer and Information Research Scientist — designing an ablation to attribute an empirical gain, budgeting an NSF CISE proposal against page and content limits, deciding what reproducibility artifacts to release with a paper, screening a draft for mathiness or terminology misuse, or scoping the consent/ethics review needed before running an experiment on real users.

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

Use when a task needs the judgment of a Chemical Technician — running a routine or non-routine lab analysis under an SOP, reading a control chart or calibration-check trend for drift, deciding whether to release, hold, or escalate a QC result, troubleshooting an instrument or reagent problem on the bench, or handling chain-of-custody and hazardous-chemical storage/documentation.

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

Use when a task needs the judgment of a Chemical Equipment Operator/Tender — deciding whether to continue or stop a reagent addition when reactor temperature exceeds its expected range, evaluating a batch record deviation's actual chemical consequence before release, following lockout/tagout before servicing equipment that processed a hazardous chemical, or verifying secondary containment readiness.

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