68건 · 관련도순
Set up a separate Git working directory for a new task or an existing branch, pull request, or commit. Detect and reuse existing isolation, prefer the agent environment's worktree tools, and report the working path and branch.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Check the Compound Engineering environment and repository settings, identify configuration issues, and report optional tools. Confirm where generated documents will be stored, make approved configuration fixes, or scaffold a Compound Pack with pack:<id>.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide an agent through searching code, logs, and configuration files by content or filename. It explains which tools to choose, how to filter searches, and how to recognize incomplete results or searches requiring shell commands.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare a separate Git working directory for feature development, then install project dependencies and run baseline tests. Check for existing isolation first, use native worktree tools when available, and otherwise fall back to Git.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize open pull requests by size, automated check results, inactivity, and overlapping files. Review selected changes in depth, prepare comments for approval, and optionally create separate local working directories for hands-on review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create a separate Git working directory for feature development without switching your current branch. The skill checks branch names and ignore settings, prepares dependencies, and starts background checks, with options for separate dependency installation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and manage Git worktrees, separate folders for working on different branches. Organize them under a shared project path, move uncommitted or stashed changes between them, copy environment files, and open them in an editor.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manage Git worktrees, separate folders for working on different branches, with commands to create, list, and remove them. Move uncommitted changes between folders, copy environment files, and open a worktree in an editor.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide team Git work with consistent commit messages, branch naming, and review practices. Follow concrete steps for everyday development, urgent fixes, releases, merge conflicts, and version tags, including guidance on when to use merge or rebase.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide team Git work with consistent commit messages, branch naming, and review practices. Follow concrete steps for everyday development, urgent fixes, releases, merge conflicts, and version tags, including guidance on when to use merge or rebase.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare a separate workspace for feature development using platform tools or git worktree, which gives a branch its own working directory. It checks existing isolation, prepares dependencies, and runs tests before implementation begins.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Pull AWS Security Agent findings (penetration tests and code reviews) and drive remediation. Use this whenever the user mentions Security Agent, security findings, pentest or penetration test results, code review findings, vulnerabilities found in their AWS account, "what did the security scan find", remediating or triaging security risks, or wants to start fixing reported vulnerabilities — even if they don't name the service explicitly. Trigger it for phrases like "get my security findings", "what vulnerabilities do we have", "let's fix the pentest results", or "triage the security report". The skill discovers scans, exports findings to a gitignored local directory (so sensitive exploit detail is never committed), produces a prioritized triage summary, and offers to start fixing the highest-risk issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prevents, detects, and remediates files that should never be committed — secrets (.env, API tokens, hardcoded credentials) and dev artifacts (build output, scratch databases, editor/OS files). Covers .gitignore (and why it does not untrack), git rm --cached, auditing tracked files, history scrubbing, and credential rotation. Use when a repo has committed secrets or junk, when setting up a new repo's ignore rules, or when reviewing what a repo actually tracks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a bounded task plan (and the agent prompt for it) that runs the 5-layer profiling methodology in .claude/skills/model-profiling/METHODOLOGY.md against one model, stops for human confirmation before any GPU work starts, then delegates the actual run to a background agent, verifies its completion claim, and routes findings into a gitignored .profiling-runs/<model>/ directory — durably tracked as a sub-issue under the tracking issue named in SKILL.md's "Result tracking" section — plus the methodology doc.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
All-in-one project configuration and health management. Sets up new projects (settings.local.json, CLAUDE.md, .gitignore), audits existing projects (permissions, context quality, MCP coverage, leaked secrets, stale docs), tidies accumulated cruft, captures session learnings, and adds permission presets. Uses sub-agents for heavy analysis to keep main context clean. Trigger with 'project health', 'check project', 'setup project', 'kickoff', 'bootstrap', 'tidy permissions', 'clean settings', 'capture learnings', 'audit context', 'add python permissions', or 'init project'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate, reconcile to the chosen target(s), and stage the `manifest.json` for a `.ppmplugin` bundle. In the normal flow the committed `./manifest.json` already exists (authored by /generate-native-extension), so this stage reads it, runs the plugin's upload-compatibility checks locally as a pre-flight gate (name regex, canonical prefix, known incompatible names, method and identifier shapes), reconciles `entrypoints` down to the platform(s) you ship, and writes the gitignored staged copy `ppmplugin/staging/manifest.json` that /assemble-ppmplugin zips. If no committed manifest exists (a hand-authored module) it falls back to deriving every field from the class name and Android module source, writing both the committed file and the staged copy. No toolchain — pure read, validate, write. Target-aware. Run after the native module exists, before the build skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when creating a new Godot 4.x project — scaffolds recommended directory structure, project settings, autoloads, and .gitignore
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
把项目推送到 GitHub，三种模式自动判断：**首次推送**（大文件扫描 → 生成 .gitignore → git init → gh 建仓 → 推送）、**日常更新**（commit + push）、**版本发布**（打 tag + 建 Release，可附下载文件）。核心原则是安全第一：推之前必扫大文件和敏感文件，宁可多问一句也不把不该推的东西推上去。当用户说"推到GitHub""推送到GitHub""git push""上传到GitHub""提交并推送""发版本""打release""打tag""/git-push"时触发。不适用于：规划哪些功能进哪个版本号（用 issue-pool——本 skill 只负责把已经定好的版本号打成 tag）、复杂 git 操作如 rebase/cherry-pick/解冲突/改历史/回滚（直接用 git 命令，本 skill 不覆盖）、代码写完前的自测和验收。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and clean up the repository — remove dead files, fix naming inconsistencies, update .gitignore, and ensure the repo is well-organized for OSS contributors. Does NOT modify source code logic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage Git repositories and collaborative workflows — branching strategies, commit hygiene, conflict resolution, pull requests, hooks, and .gitignore management. Use when the user requests version control or provides relevant inputs for this workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Initialize GitHub repositories with standard files and configuration. Generates LICENSE, CONTRIBUTING.md, SECURITY.md, issue/PR templates, CI config, and .gitignore. Detects project type and adapts templates accordingly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepare a git repo before new work: review uncommitted changes, fix .gitignore, delete merged branches, end on clean main, or inspect one branch before deciding. Don't use for dead code, commit-and-push, releases, LICENSE files, or git how-tos.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bootstrap Trigger.dev into an existing project from scratch: authenticate the CLI, install @trigger.dev/sdk and @trigger.dev/build, write trigger.config.ts with the project ref and task dirs, scaffold a /trigger directory with a first task, wire tsconfig and .gitignore, set TRIGGER_SECRET_KEY, and run the dev server. Load this when a project has no trigger.config.ts yet and the user asks to "add Trigger.dev", "set up Trigger.dev", "initialize Trigger.dev", or get a first task running, including in a monorepo. Once the project is set up and you are writing task code, switch to the trigger-authoring-tasks skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prevents private infrastructure details (node hostnames, internal project names, local usernames and personal emails, absolute home paths, private and VPN IP ranges) from leaking into public repositories through commits, PRs, docs or release artifacts. Use when working in a public or soon-to-be-public repo, before commits or releases, when writing deployment docs for an OSS project, or when the user asks to "set up the privacy guard", "install privacy-guard", "check for leaks", "protect this public repo". Bootstraps a pre-commit hook backed by a gitignored local denylist plus gitleaks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.