「repo」の検索結果

Set up and optimize repositories for AI coding agents. Creates minimal AGENTS.md, CLAUDE.md symlink, docs/REQUIREMENTS.md, docs/BUSINESS-RULES.md, feedback loops, and deterministic enforcement (Claude Code hooks, OpenCode plugins). Use when user wants to make a repo AI-friendly, set up AGENTS.md/CLAUDE.md, document requirements/business rules for AI, add pre-commit hooks for AI workflows, or optimize codebase structure for coding agents.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Coveralls — coveralls coverage tracking management. Covers coverage reporting, PR status checks, repository configuration, coverage history, and badge management. Use when managing Coveralls coverage reports, configuring coverage thresholds, debugging coverage uploads, or analyzing coverage trends.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Aws Codecommit — aWS CodeCommit repository management and analysis. Covers repository inventory, branch details, pull request status, commit history, approval rules, and trigger configurations. Use when inspecting repositories, reviewing pull requests, auditing branch policies, or analyzing commit activity.

日本語の概要は準備中です。原文の説明を表示しています。

Sync local skills repository with upstream changes from obra/superpowers-skills

日本語の概要は準備中です。原文の説明を表示しています。

Run or maintain the full tdmcp repo quality-audit team: command sweeps, all package/Makefile/CI gates, security review, usability/flow review, refactor/test-gap analysis, coverage hardening, QA, and follow-up fix waves. Use whenever the user asks for a complete audit, improve repo/code quality, test all commands, find security/usability failures, refactor debt, add missing tests, re-run the audit, continue a previous quality wave, or verify the repo is ready.

日本語の概要は準備中です。原文の説明を表示しています。

Run a security sweep over one repo: secrets, dependencies and the diff, a security review and a silent-failure hunt, one deduped and ranked findings report, issues filed for blocking findings only after GO, each one handed to pb-bug-fix. Use for "security sweep", "audit this repo", "check for leaked secrets and vulnerable deps".

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

SharePointからExcelファイルをダウンロードする

Generates IEEE-format LaTeX technical reports from project requirements and codebase evidence, using academic prose, pseudocode-only explanations, BibTeX references, and IEEEtran formatting.

日本語の概要は準備中です。原文の説明を表示しています。

実装が他リポジトリのコードの挙動に依存する仮定を、依存先の実コードで確証する。クロスリポジトリ依存が無い場合は使用しない。Triggers on: '/cross-repo-verify', 'クロスリポジトリ依存を確認', 'クロスリポジトリの確証'

レポートコンパイルエージェント - 分析結果のMarkdownファイルを統合HTMLレポートに変換。/compile-report [出力パス] で呼び出し。

Extract and catalog attack patterns from cyber threat intelligence reports into a structured STIX-based library mapped to MITRE ATT&CK for detection engineering and threat-informed defense.

日本語の概要は準備中です。原文の説明を表示しています。

GitHub repository management — triage PRs/issues, check Actions status, manage branch protection, tag releases, housekeeping (stale branches, stashes), CODEOWNERS, badges, and repo hardening. Use when the user asks about GitHub, PRs, CI/CD status, repo health, branch protection, releases, or any GitHub operations.

日本語の概要は準備中です。原文の説明を表示しています。

Validates predictive models on omics and biomedical data with nested cross-validation, group/batch/temporal-aware splits, the full data-leakage taxonomy, probability calibration, decision-curve net benefit, optimism correction, sample-size planning, and TRIPOD+AI reporting. Use when estimating model performance honestly, choosing a CV scheme, detecting leakage, or judging whether reported discrimination means the model is actually useful. For feature selection itself see machine-learning/biomarker-discovery; for confirmatory-trial inference see clinical-biostatistics/trial-reporting.

日本語の概要は準備中です。原文の説明を表示しています。

Apply the aoa-safe-infra-change workflow inside an abyss-* repository using repo-relative operational surfaces, explicit local authority notes, rollback posture, and local validation commands. Use when the base infra-change workflow is correct but a thin project overlay is needed for one abyss repo. Do not use when the base skill is sufficient without local adaptation or when the task is really about producing a shareable artifact.

日本語の概要は準備中です。原文の説明を表示しています。

Turborepo (高速モノレポビルドシステム) リファレンス。 turbo.json、turbo run、タスク依存 (dependsOn)、キャッシュ (local / remote)、 workspaces (pnpm / npm / yarn / bun)、--filter、Remote Cache (Vercel)、 parallel 実行、turbo gen (コード生成)、watch モード、 エラーメッセージ診断 (recursive turbo invocations, missing root task, invalid env prefix)。

会話の成果 (調査・比較・解説など) を人が判断するための HTML レポートにまとめ、crit preview で開いてコメント対応まで往復するスキル。ユーザーが「HTML にまとめて」「レポートにして」「crit で開いて」「/crit で表示して」など、HTML 化して crit で見る意図を示したら必ず使用する。dev パイプラインの成果物 (research / plan / report.html) は対象外。

Activate when the user asks about any repository listed in the system prompt under 'OpenViking — Indexed Code Repositories', or when they ask about an external library, framework, or project that may have been indexed. Also activate when the user wants to add, remove, or manage repos. Always search the local codebase first before using this skill.

日本語の概要は準備中です。原文の説明を表示しています。

Supply chain investigation, evidence recovery, and forensic analysis for GitHub repositories. Covers deleted commit recovery, force-push detection, IOC extraction, multi-source evidence collection, hypothesis formation/validation, and structured forensic reporting. Inspired by RAPTOR's 1800+ line OSS Forensics system.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"

日本語の概要は準備中です。原文の説明を表示しています。

Produce a deterministic, read-only evidence map of the repository for SDD Composy (languages, manifests, commands, modules, boundaries, staleness) and publish the context bundle only on request. Use before a PRD or TechSpec, or when the map is stale — 'mapear o repositório', 'atualizar o contexto do código', 'what does this codebase look like for SDD'. Do NOT use for architecture decisions, code review, or repository exploration without an SDD workspace.

日本語の概要は準備中です。原文の説明を表示しています。

Two-phase memory hygiene. Phase 1: scan external Claude Code memory (~/.claude/projects/<slug>/memory/) for durable rules to migrate into the repo and entries already duplicated by repo atoms. Phase 2: audit in-repo memory/, CLAUDE.md, docs/architecture/, and docs/sections/ for dead links, duplication, drift, and bloat.

日本語の概要は準備中です。原文の説明を表示しています。

Build a "product description" repo for a software product — a set of prose documents describing, from the outside in, what the user sees, what they can do, and exactly what happens when they do it, written from the code and tests, then verified against the running product and triaged into a bug list. Works for any product with a user (canvas editors, web apps, CLIs, chat products, mobile apps). Use when the user asks to "write a product description for X", "describe the user experience of X", "document how X behaves for the user", "make a behavior-spec repo", or wants a feature-by-feature, event-by-event account of an app's behavior rather than API docs. Also use to resume or extend an existing product description repo.

日本語の概要は準備中です。原文の説明を表示しています。

Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does not apply fixes.

日本語の概要は準備中です。原文の説明を表示しています。