'release' 검색 결과

VK Blocks Pro をリリース・デプロイする際に使用する。バージョン番号の付与、タグの push、GitHub Actions による CI/デプロイのワークフローを管理する。

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

Passive, pattern-calibrated risk discovery for authorized security research over an open-source project, repository URL, dependency, release, or local checkout. Use when the security research agent needs to find highest-risk areas, map attack surface, identify likely bug-hunting targets, prioritize security review, inspect structural/logical/security-critical code, compare vulnerable versus patched versions, reason from broad high-severity vulnerability families, or remember areas of interest for later attack-chain research.

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

Cycle-end retrospective converting recurring judgment failures into durable enforcement. Reviews the cycle's friction — repeated user corrections, guard trips, RCA themes, integrate failures — and turns each recurring one into a landmines.md entry, then proposes graduation candidates up the enforcement funnel (landmine → advisory hook → hard gate). Pairs with standup: standup says what shipped and what's next; retrospective says what kept going wrong and how to stop it structurally. Writes only memory entries and a report — graduation proposals are advisory and require the normal seed.md amendment path to become enforcement. Invoke at the end of a release cycle, an epic, or any stretch of work with repeated friction.

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

배포. release 브랜치 main 반영, 빌드 검증, push 실행. .claude/skills/deploy 기준

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

Stage and verify Fusion exports, drawing PDFs, flat-pattern DXF, viewport images and local renders. Use for engineering deliverables, not automatic publication or release.

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

Inspect scoped Autodesk data, compare versioned BOMs, and prepare ownership-aware drafts or approved custom-property changes. Not for implicit PLM release, membership changes or CAD geometry editing.

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

Prepare a traceable local Fusion engineering review draft with source identities, artifacts and unresolved assurance gates. Not for sending, publication or release approval.

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

Plan and implement infrastructure, CI/CD, container, deployment, observability, and operational configuration changes with least privilege, staged validation, and rollback awareness. Use for pipelines, infrastructure as code, Kubernetes, containers, release automation, monitoring, and production-readiness work; do not use to perform destructive production actions without explicit authorization.

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

Clone/create/fork repos; manage remotes, releases.

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

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

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

Review a planned deployment or release diff for rollback feasibility, mixed-version compatibility, migrations, and configuration readiness without deploying it.

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

Challenge vision alignment, value, cost, risk and operating ownership at material scope or release decisions.

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

Use when auditing a repository for evidence-backed gaps between code, SPECs, architecture, and documentation — before a release, after a review, or when the user asks what is missing or divergent. Confirmed gaps become Draft SPECs via write-specs, a tracked GitHub Epic via create-issues, and orchestrated execution via orchestrator, with an explicit approval gate before any external action.

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

Go / no-go gate before any deployment. Checks failure modes, rollback plan, cost, production bar, and definition of done. Trigger before releasing to any environment that carries real consequences.

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

Use when configuring or optimising GitHub repositories for cost-effective, consistent operations — CI triggers, Actions billing, issue tracking, labelling, branch protection, or release workflow.

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

公開CLIツールのリリース作業(バージョン付け・利用者向けドキュメント・CHANGELOG・検証・PR・タグ)を、ツール公開手順の規約に従って進める。ツールをリリースするとき、バージョンを上げて公開するとき、リリースPRやタグを作るときに使用する。

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

Bump the package version and create an annotated git tag. Accepts a semantic version number (1.2.0) or a bump type (patch, minor, major). Does not push — use the publish skill to push. Use as part of a release workflow.

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

Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.

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

Find overly complex code: files over 300 lines, functions over 50 lines, deeply nested conditions (4+ levels), and magic numbers. Use for code quality reviews, pre-release checks, or when asked to assess code maintainability.

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

Audit npm or pip dependencies for outdated packages and known vulnerabilities. Use when checking package health, preparing for a release, reviewing dependencies before merging a PR, or when asked about outdated packages or security advisories.

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

Run a comprehensive code quality audit covering security, performance, and maintainability. Use for quarterly audits, pre-release reviews, or when onboarding to a large codebase.

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

Use before merging a release-shaped PR — pre-merge checklist, rollout plan, rollback criteria, ops handoff. Triggers on 'ready to ship', 'launch checklist', 'rollout plan for X'.

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

Use when building or maintaining a Composer library — versioning, Laravel integration, autoloading, publishing to private registries — even when the user says 'release a new version'.

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

Run an infrastructure-first security audit of a repository - secrets archaeology, dependency supply chain, CI/CD pipeline, LLM/AI attack surface, agent skill supply chain, OWASP Top 10, STRIDE threat model, and data classification - with a confidence gate and a pre-emit verification gate that suppress speculative findings. Use when asked for a security audit, threat model, pentest-style review, OWASP pass, or a pre-release security check. Not for reviewing a single diff - use requesting-code-review for that.

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