'github' 검색 결과

Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security, Availability, Processing Integrity, Confidentiality, Privacy) with automated evidence gathering from AWS, Azure, GCP, Okta, GitHub, and Jira. Use when preparing for or maintaining SOC 2 Ty...

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

OSINT kişi araştırması — sosyal medya, EXIF, bcrypt crack, geolocation

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

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

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

Review PRs: diffs, inline comments via gh or REST.

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

MANDATORY deploy after every code change. Typecheck → deploy → purge CDN → E2E on production → visual verify → fix-forward loop. Workers Builds native CI/CD, D1 Time Travel PIT recovery, D1→R2 long-term backups, wrangler rollback, wrangler secrets management, structured observability, cross-browser smoke tests, rollback procedures, and GitHub auto-configuration.

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

Run a project's GitHub Issues through Orca Workers from a coordinating session in the project's Hub folder. The Orchestrator reads Issues, claims one, dispatches an Orca Task into a fresh worktree of the target repo, supervises until worker_done, and writes the outcome back to the Issue — it never edits code itself. Use when the user says "take

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

Vendor (copy-import) a single external Claude Code skill into your own skills repo correctly — with license compliance and full provenance/attribution. Deterministic, idempotent primitive: given an upstream ref (owner/repo/path@sha or a GitHub URL) it fetches the skill, detects and gates on the license, copies the folder, injects a provenance frontmatter block (license + metadata: author/source/upstream_commit/vendored_at/provenance), ships the upstream LICENSE, adds a ## Credits section, and records a CREDITS.md ledger entry. Use when the user asks to "vendor a skill", "import a skill", "clone a skill", "borrow someone's skill", "add an external skill with attribution/credit", or スキルを取り込む / vendoring / 他人のスキルを自分のリポに取り込む. This is the import primitive that a skill-scout/curator orchestrator calls; it does NOT discover or evaluate — it correctly imports ONE skill you already chose.

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

Automatically consume open GitHub issues one by one. Fetches the oldest open issue, delegates implementation to the issue-implementer agent, runs code review via the code-reviewer agent, iterates on feedback, merges the PR, and moves on to the next issue. Invoke with `/auto-issue-worker`.

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

Publish agent skills AND MCP servers to every marketplace, plugin directory, and registry — security-scan for private data, validate with `gh skill`, cut a release, wire the Claude /plugin and Codex marketplaces, publish an MCP server to the official MCP Registry (mcp-publisher + server.json), and prep the curated / monetized stores (Buda Marketplace, Agensi, OpenClaw ClawHub) and review-gated directories (ChatGPT App Directory, Anthropic Connectors + Desktop Extensions/.mcpb). Use when the user wants to publish, release, list, 上架, or distribute agent skills, plugins, or MCP servers to skills.sh / SkillsMP / Claude Code / Codex / the MCP Registry.

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

Design a GitHub social-preview card (og:image, 1280x640) for a repository. Use when the user asks for a social preview, repo cover, og image, link card, opengraph image, or README hero. Five editorial moods (editorial, poster, blueprint, gallery, terminal), CJK-first typography, one self-contained HTML file, deterministic checks, crisp PNG export. No image model needed.

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

uv (Astral 製 高速 Python パッケージ / プロジェクトマネージャー) のリファレンス。 pyproject.toml, uv.lock, uv init / add / sync / run / lock, uv pip, uv venv, uvx / uv tool, uv python install / pin, PEP 723, tool.uv.sources, uv build / publish, uv_build, uv.toml, UV_* 環境変数, uv auth, Docker / GitHub Actions / PyTorch 連携。

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

Kotlin Multiplatform (KMP) / Compose Multiplatform (JetBrains, Kotlin) の公式リファレンス。 expect/actual, source set hierarchy, Multiplatform Gradle DSL, org.jetbrains.compose, Compose Resources (Res), Compose for iOS / Compose Desktop (Window, Tray, MenuBar, nativeDistributions) / Web, iOS 統合 (SwiftPM export, CocoaPods), Navigation / ViewModel / Lifecycle, Compose Hot Reload, Kotlin Toolchain, CI (GitHub Actions / TeamCity), Maven Central / npm 公開, AGP 9 移行, 互換性表。

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

Generate release notes from merged PR history and commits. Categorizes changes by type and creates GitHub releases with semantic versioning. Use when the user asks to create a release or generate release notes (e.g., "リリースノート", "release note", "リリース作成"). Do NOT use for changelogs, commit summaries, or PR descriptions.

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

Unified pull request workflow: prepare a safe branch, run read-only review, fix Required findings, create/update a GitHub draft PR, and verify CI plus automated review comments. Subcommands: `create` (simplify + PR, skip code review), `review` (read-only findings only), `fix` (Required fixes + commit, no push), `simplify` (simplification only), `verify` (existing PR checks/reviews only). Use when creating or reviewing PRs, self-reviewing changes, simplifying PR changes, or requesting "PR作成", "レビュー", "簡素化". Do NOT use for responding to review comments or a lightweight review of the current working diff without the PR workflow (use the built-in /code-review instead).

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

Monitor PRs, fix CI failures, address review comments, resolve merge conflicts, and restack stacks. Supports independent PRs, Graphite stacks, and GitHub stacked PRs (gh-stack).

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

CI/CD pipeline design, GitHub Actions workflows, deployment automation, infrastructure as code, and release management. Use when setting up CI/CD, automating deployments, configuring build pipelines, or managing releases.

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

Set up a GitHub Actions CI/CD pipeline with linting, testing, type-checking, and deployment steps.

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

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

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

Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".

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

When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel. Use for multi-job CI failures where jobs are independent.

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

Install or update ToolUniverse in Claude Science — create the conda env, install the tooluniverse pip package, and (re)build the tooluniverse-research skill by fetching the current workflow library from GitHub. Use for first-time setup, upgrading the ToolUniverse version, refreshing the bundled workflows after an upstream release, or reinstalling on a new machine.

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

Fetch external documents linked in SCF submissions — Google Docs, Google Drive PDFs, GitHub, Notion, IPFS. Use when a submission links to an architecture doc, whitepaper, or technical spec hosted externally. Handles URL transformation for Google services.

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

Triage application logs, open GitHub issues, pending feedback, in-app Issues, and agent conversations. Runs five phases: logs → close shipped issues → feedback → in-app issues → agent FAQ gaps. Use when /whats shows pending feedback, checking app logs, cleaning up shipped issues, or working the in-app Issues backlog.

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

Review code changes against linked GitHub issue specs to catch implementation drift — building something plausible but wrong. Checks each acceptance criterion against actual code.

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