Results for “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.

The English summary is being prepared. Showing the original description.

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

Review concrete code changes for defects, compatibility problems, repository-rule violations, and unnecessary code. Produce evidence-based findings and, when explicitly requested, make minimal cleanup changes while checking that existing behavior is preserved.

• Reviewing a pull request or commit range
• Inspecting staged and unstaged changes
• Finding debug residue and duplicate code

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.

The English summary is being prepared. Showing the original description.

Create or revise skills shipped within the Hermes Agent repository. The guidance covers file placement, required metadata, clear procedures, platform checks, tests, and documentation updates so contributions follow the repository’s authoring standards.

• Add a reusable skill to the Hermes Agent repository
• Revise an existing in-repository SKILL.md
• Choose bundled or optional placement

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

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

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

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

Set up a consistent local environment for developing ClawTeam, then validate changes with focused tests and real agent workflows. Includes scripts for connecting other projects to local skills and guidance for investigating coordination bugs.

• Set up a consistent local development command
• Reproduce worker startup or messaging bugs
• Validate agent coordination after code changes

Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.

• Reviewing git operations after repository checkout
• Checking tokens for private cross-repository access
• Reviewing sparse and shallow checkout changes

Set up an Obsidian knowledge base for a research repository containing code and Markdown. It creates project links, planning notes, source inventories, and code summaries, importing structure and summaries while leaving large research artifacts out.

• Starting a research project's knowledge base
• Bringing a code and Markdown project into Obsidian
• Creating project plans and source inventories

Audit an entire repository with four parallel agents checking documentation, hook scripts, skills, and rules. Identify broken references, incorrect counts, code issues, and conflicting information, then apply fixes and repeat verification for up to five rounds.

• Check repository consistency after broad changes
• Find broken paths and outdated feature counts
• Review hook scripts and rule consistency

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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`.

The English summary is being prepared. Showing the original description.