'repository' 검색 결과

リポジトリの構造・技術スタック・機能一覧・セットアップ手順を動的に解析し、 包括的なドキュメントを自動生成するスキル。言語・フレームワーク問わず汎用的に動作する。 Use this skill whenever the user asks to: - Explain a repository / リポジトリの説明 / リポジトリの概要 - Generate a README / README生成 / README作成 - Understand project structure / プロジェクト構成を教えて / 構造を説明して - Learn how to run a project / 使い方を教えて / 動かし方 / セットアップ方法 - Get a repo overview / repo overview / explain this repo / what does this repo do - List features / 機能一覧 / このプロジェクトは何ができる？ - Onboard to a new codebase / コードベースのキャッチアップ / 新しいリポジトリに入った - "このリポジトリ何？" "プロジェクトの全体像" "how to run this project" - "コードの全体を把握したい" "ドキュメントを整備して" "技術スタックを知りたい" This skill is especially useful when joining a new project, onboarding team members, or when a repository lacks proper documentation. It works with ANY repository regardless of programming language, framework, or project type.

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

Create, update, or reuse a repository threat model: a document describing its architecture, attacker capabilities, trust boundaries, and potential security failures. The result is a Markdown reference grounded in the repository's actual code and scope.

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

• Documenting architecture and trust boundaries
• Creating or updating a repository threat model
• Preparing a threat model for a specific security review

Create, update, or reuse a repository threat model: a document describing system architecture, attacker capabilities, trust boundaries, and potential security failures. Produce a Markdown model grounded in source evidence for standalone use or a security scan.

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

• Creating a threat model for a repository
• Updating a model after architecture changes
• Preparing a model for a security scan

Audit, rename, and polish a GitHub repository across its local checkout and remote settings. Use when Codex needs to synchronize a local and GitHub repository name, set the description, homepage URL, or topics, create repository branding and a GitHub social preview, restructure a README, or prepare and publish a cohesive repository identity. Uses GitHub CLI for supported remote operations and delegates visual identity work to $create-context-aware-logos.

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

Hermes Agent 저장소에서 배포할 스킬을 공통 규약에 따라 만들고 수정합니다. 저장 위치와 SKILL.md 구성부터 테스트, 관련 문서 갱신까지 다룹니다.

• 재사용할 절차를 저장소 스킬로 정리
• 기존 SKILL.md 수정
• 기본 포함과 선택 설치 위치 결정

Create a reusable snapshot of an existing code repository, covering files, imports, components, and routes. It gives agents a shared reference for migration and editing work without repeatedly scanning the directory tree.

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

• Prepare repository structure for a code migration
• Record components and routes before making changes
• Reuse a repository snapshot across agent turns

Build an HTML dashboard for a public GitHub repository, showing stars, forks, contributors, issues, pull requests, and recent activity. Choose a standalone page or source files that support updates and record where the data came from.

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

• Review a repository's activity in one dashboard
• Prepare an open-source project health report
• Check leading contributors and recent issues or pull requests

Move media assets from a Remotion repository to Cloudflare R2, update source references to public URLs, and verify that uploaded files match the originals before removing local copies.

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

• Moving repository media assets to Cloudflare R2
• Updating source references to hosted media URLs
• Verifying uploaded files before deleting local copies

Create GitHub issues that follow the current repository's templates. The skill selects the appropriate report format, collects required information, and prepares the title, body, labels, and issue type for review before submission.

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

• File a bug report using the repository's template
• Submit a feature request with required details
• Create an internal engineering task as a maintainer

Delegate scoped repository analysis or implementation to DeepSeek Harness without opening its interactive interface. Collect its final text, check the exit status, and inspect repository changes when the task requires read-only work.

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

• Diagnose a failing test without editing files
• Delegate a scoped repository investigation
• Request implementation in a specified project

Prevent recurring coding-agent mistakes by turning repository evidence into specific instructions, automated checks, regression tests, and failure records. Also checks whether guidance has become outdated and documents changes, verification results, and follow-up work in an adoption report.

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

• Create agent instructions tailored to a repository
• Turn recurring mistakes into regression checks and failure records
• Detect outdated guidance and broken verification commands

Record recurring setup and workflow problems that a repository can fix, so future contributors can avoid the same friction. Also review existing entries, remove duplicates, prioritize useful fixes, and preserve a history of resolved problems.

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

• Recording confusing setup steps
• Tracking recurring problems in repository scripts
• Deduplicating and prioritizing friction reports

Understand a public GitHub repository through GitDiagram's architecture overview. Get an explanation of its main components, source paths, and connections, plus Mermaid diagram source and an interactive diagram for exploring the code.

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

• Getting an overview of an unfamiliar public repository
• Finding source paths for major components
• Understanding connections and data flow

Inspect repository code or code changes for plausible security vulnerabilities. The skill records candidate issues with affected locations, attacker-controlled inputs, failing safeguards, and possible impact, preserving the evidence needed for later validation.

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

• Finding security issues that may arise from code changes
• Investigating vulnerability candidates in repository code
• Organizing source evidence for later validation

Audit an entire repository or a selected folder, package, or path in one review pass. Produce a security report with source evidence, severity assessments, and clear coverage limits, including unresolved questions that need further investigation.

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

• Run a standard security audit of a repository
• Review a selected folder or package
• Check findings alongside evidence and coverage gaps

Audit a repository or selected source paths for security issues in a single pass. Produce a report with source evidence, severity, possible attack paths, validation results, and an honest account of what was reviewed.

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

• Run a standard security audit across a repository
• Review one package or folder for security issues
• Audit source code against a supplied threat model

Use this skill when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually works end-to-end. Use the repository bootstrap scripts to standardize the local `clawteam` command and to wire project-local `.agents` and `.claude` skills back to this repository. This skill is repository-development oriented, not a general end-user usage guide.

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

Review or de-slop concrete changes in ccch1mneyyy/dsh-TUI at maintainer level: PR numbers or URLs, branches, commit ranges, patch files, staged or unstaged worktrees, and scoped repository-hygiene requests. Use for evidence-first correctness, contract, repository-rule, process, and behavior-preserving cleanup review, including debug residue, dead or duplicate code, speculative abstractions, stale comments or tests, and unrelated diff churn. Do not use for abstract designs with no concrete repository artifact; use audit for repository-wide assessments and vuln-check for security-only checks.

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

Apply minimal MCAF repository governance when the user explicitly asks to adopt MCAF or change MCAF-specific rules. USE FOR: creating or tightening root and local AGENTS.md policy; placing durable engineering context; defining the repository's own verification contract. DO NOT USE FOR: ordinary .NET implementation, documentation edits, UI/UX, testing, CI, Git, NFR, developer-experience, or ML work unless the request is specifically about MCAF governance. INVOKES: inspect repository policy and documentation, make the smallest durable governance change, then validate the affected repository surfaces.

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

Routes substantive ML, AI, data, scientific-computing, and software-engineering requests to the smallest useful set of managed repository skills. Invoke proactively when a request names or implies a package, framework, model family, dataset, modality, workflow, backend, deployment target, evaluation method, or implementation approach that may benefit from repository guidance, even if no repository is named. Narrow progressively from area to family to repository root: inspect only the one or two most likely area pages; compare candidates by capability, task surface, model/data format, training versus inference versus evaluation intent, runtime constraints, and root-skill description; then open only the selected root and relevant sub-skills, references, or scripts. Select multiple repositories only when each adds a distinct capability. Do not load the whole collection, treat dependencies or incidental integrations as capabilities, choose by name alone, or force a match when no exact taxonomy family applies.

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

Generate AI-friendly repository documentation with the SourceSage CLI. Use when Codex needs to run `sage` or `sourcesage` to create `.SourceSageAssets/Repository_summary.md`, analyze the current repository or another local repository, switch the output language between English and Japanese, use `--lite` to keep the summary small, change the output directory, or optionally create a deprecated tag-diff release report with `--diff`.

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

Generate AI-friendly repository documentation with the SourceSage CLI. Use when Codex needs to run `sage` or `sourcesage` to create `.SourceSageAssets/Repository_summary.md`, analyze the current repository or another local repository, switch the output language between English and Japanese, use `--lite` to keep the summary small, change the output directory, or optionally create a deprecated tag-diff release report with `--diff`.

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

기술 문서와 에이전트·기여자용 지침 파일을 작성하고 검토합니다. 설명과 운영 절차, 다국어 버전의 일관성을 확인하고 근거가 충분한 문제를 수정합니다.

• 기술 문서 작성 및 갱신
• README와 문서 변경 사항 검토
• 에이전트 지침과 기여 절차 정리

Set up a Paperclip maintenance bot that applies a chosen skill to a repository and opens pull requests. Configure its agent, schedule or event trigger, work limits, reviewers, and readiness checks before activation.

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

• Schedule nightly repository maintenance
• Trigger maintenance from webhook events
• Assign maintenance to an existing or new agent