3.2천건 · 관련도순
Guide for creating or updating effective portable skills with specialized knowledge, workflows, or tool integrations. Use for Codex, Claude Code, GitHub Copilot, or shared-catalog skill work after selecting the target host and installation path.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add authentication and user management to a Netlify site with @netlify/identity — signup/login/logout, OAuth social login (Google/GitHub/GitLab/Bitbucket), server-side user verification in Functions, role-based access control (RBAC), admin user management, and Identity event hooks. Use when adding a login/signup flow, "add social login", gating content by user role, protecting a function or page behind auth, assigning roles at signup, customizing auth emails, or handling OAuth/confirmation/recovery callbacks. Not for locking an entire site to a company/team — that is netlify-access-control.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Look up and read Hugging Face paper pages in markdown, and use the papers API for structured metadata such as authors, linked models/datasets/spaces, Github repo and project page. Use when the user shares a Hugging Face paper page URL, an arXiv URL or ID, or asks to summarize, explain, or analyze an AI research paper.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure deployment for web apps — Static Web Apps, App Service, Blob Storage, Bicep/ARM, GitHub Actions CI/CD. Use when deploying Next.js/Vite to Azure or configuring Azure resources for full-stack apps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Git operations, shell scripting, CI/CD pipelines, and terminal automation. Use for conventional commits, PowerShell/Bash scripting, configuring GitHub Actions, or automating development tooling workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepare a project for open sourcing: a sanitized fork with secrets and internal references stripped, a sanitizer verdict, README and LICENSE, then a new PRIVATE GitHub repo created and pushed only after GO. The playbook never makes the repo public. Use for "open source this project", "make a sanitized fork", "prepare a public release".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Start a new private GitHub project the AOS way: create the private repo, bootstrap AOS (project card, AGENTS.md, wiki, memory, CI choice), push after GO, and confirm the first CI run is green and the repo is still private. Use for "new project", "start a repo", "bootstrap a project".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a GitHub issue into a tested fix on a branch with an open PR: read the issue as the contract, find the root cause, write the failing test first, fix, prove it, review the diff against the issue, push and open the PR only after GO. Merging stays with pb-ship. Use for "fix issue 42", "bug fix from this issue", "turn this issue into a PR".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Production-ready patterns for building LLM applications, inspired by [Dify](https://github.com/langgenius/dify) and industry best practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a PR or git range needs a visual recap page for a reviewer, with a changed-files tree, per-file notes, a Verified vs Not verified table, risks, and optional before/after images. Local and informational; never posts to GitHub.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when authoritative design system, standalone HTML template, and automated GitHub Pages live hosting workflow for creating neutral, enterprise-grade developer documentation and user manuals in the official Google Antigravity / BDB OS aesthetic ...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert changelogs, release notes, and version updates into Ozor.ai video prompts. Use this skill whenever the user has a CHANGELOG.md, release notes, GitHub release, version bump summary, or any list of product changes and wants to turn them into a video. Trigger on phrases like 'video from my changelog', 'release notes video', 'make a video from this update', 'announce this release', 'version update video', 'what's new video', 'product update video', 'feature release video', or any request to transform a list of product changes into video format using Ozor.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Craft a single, high-quality GitHub issue from a developer's description of a bug, unexpected behavior, or desired enhancement. Walks through reproduction, codebase exploration, and structured drafting so the issue is actionable on arrival. Use when user wants to file an issue, report a bug, request a feature, or document a problem they've encountered.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
オープン PR の一覧を優先順位付きで表示する。「PR 一覧」「PR リスト」「オープン PR」「PR を見せて」「プルリク一覧」「レビュー待ち PR」「PR 確認」などで起動。レビュー状態と優先度順にソートして表示。「マージ済みも」「自分の PR」などの絞り込みは発話から判断する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
新しい worktree を作成する。「worktree 作成」「worktree を作って」「worktree 切って」「Issue から worktree」「作業用 worktree」「gtr new」などで起動。Issue 番号・ブランチ名の直接指定・コンテキストからの自動命名に対応。一覧・削除・クリーンアップは shiiman-git:worktree。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
自分の PR に付いたレビューコメントを確認し、修正対応を実行する（PR作成者向け）。「レビュー対応」「レビューコメント確認」「指摘を修正」「PRコメント確認」などで起動。「修正して」と伝えれば指摘の修正まで実行する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
オープン Issue の一覧を優先順位付きで表示する。「Issue 一覧」「Issue リスト」「オープン Issue」「Issue を見せて」「チケット一覧」「未解決 Issue」「Issue 確認」などで起動。優先度順にソートして表示。「クローズ済みも」「自分の Issue」などの絞り込みは発話から判断する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
現在のブランチから PR を作成または更新する。「PR 作成」「PR を作って」「プルリク作成」「pull request」「PR 出して」「プルリクエスト」「レビュー依頼したい」「PR 更新」などで起動。変更内容を分析し適切な PR を生成。「ドラフトで」「develop 向けに」などは発話から判断する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
feature ブランチを作成する。「ブランチ作成」「ブランチを作って」「新しいブランチ」「feature ブランチ」「Issue からブランチ」「作業ブランチを作成」「ブランチ切って」などで起動。Issue 番号・ブランチ名の直接指定・コンテキストからの自動命名に対応。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Install, update, trust, or inspect Codewhale skills from GitHub or local skill folders. Use when the user asks for available skills or wants a community skill installed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert Convex Auth setup, production, OAuth, security, and debugging guidance. Use when adding or auditing Convex Auth, configuring GitHub/Google/Apple OAuth, setting auth env vars, protecting Convex functions with getAuthUserId, debugging callback URLs, preparing production auth, rotating keys, or reviewing auth security.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for pull-request, merge, version and release mechanics in the Syntropic137 repo, and for CI or release-pipeline failures. Trigger phrases include "open a PR", "submit my changes", "address the review comments", "Copilot left comments", "merge this PR", "push this nit straight to main", "CI is red", "the release gate failed", "smoke test broke", "why is this PR BLOCKED", "bump the version", "cut a release", "release v1.x", "write the release notes", "main -> release PR", "approve the release gate", "the release published a bad asset", "triage the open PRs", "PR backlog", "which PRs are ready to merge", "merge order", "DORA metrics", "deploy frequency", "lead time", "change failure rate", "time to restore", "why didn't the issue auto-close". Covers trunk-based `main`, the `release` branch, local gates (`just qa-ci`, `just preflight`), GitHub Actions gates, review and merge policy, and post-release verification. Do NOT use for deciding what to dispatch, running the orchestrator loop, or deciding when to deploy a beta or run a pit stop (see `orchestrating`); for whether a task belongs in a workspace or locally (see `dogfooding`); for using the `syn` CLI as an end user (see the syntropic137 plugin skills).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when deciding WHERE to do work on Syntropic137 itself - "run this through Syntropic", "dispatch a workflow", "should this go in a workspace or local", "kick off a run on the Mini", "dogfood this", "build Syntropic inside Syntropic", "why did the agent's push fail", "can an agent run our QA", "the execution says completed but nothing shipped". Covers what a workspace agent can and cannot do, why `.github/workflows` pushes must come from the local machine, how to write a task prompt that does not repeat a known failure, and how to verify a run actually delivered. Do NOT use for PR/release mechanics (see `devops`), for using the `syn` CLI as an end user (see the syntropic137 plugin skills), or for authoring workflow YAML.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for testing conventions and CI pipelines — unit tests, integration smoke tests, pytest markers, and GitHub Actions workflows. Use when the user asks about testing, CI, running tests, or adding tests for a recipe.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.