meta-introspector/cargo-vendormod

skill-importer

Import skills from all agent formats and regenerate unified forms. Use when adding new skills, syncing cross-agent docs, or normalizing existing skill files.

原文の言語: 英語

skill-importer

Import skills from all agent formats and regenerate unified forms. Use when adding new skills, syncing cross-agent docs, or normalizing existing skill files.

原文の言語: 英語

cargo-vendormod-atlas

Classify repositories using finite simple group theory and generate mathematical atlases. Use with atlas binaries and ZKperf coverage runners.

原文の言語: 英語

cargo-vendormod-graph

Build, analyze, partition, and visualize Rust dependency graphs with cargo-vendormod. Use for global-graph commands.

原文の言語: 英語

cargo-vendormod-multi-lang

Detect languages and generate per-language Nix flakes with cargo-vendormod. Use when processing Java, JavaScript, C, Lean4, Python, Go, Ruby, Nix, or mixed-language projects.

原文の言語: 英語

cargo-vendormod-processing

Process Rust crates in layered topological order and generate Nix flakes. Use with the `processing` binary and `workflow` runner.

原文の言語: 英語

cargo-vendormod-reporting

Generate, process, and verify reports and manifests with cargo-vendormod. Use for report generation, goal tracking, coverage summaries, gitmodules metadata, rollup locks, Cargo.toml fixes, and DASL metadata processing.

原文の言語: 英語

cargo-vendormod-scanner

Discover and classify repositories, crates, and sanitized references in cargo-vendormod workloads. Use when scanning directories for Cargo.toml files, collecting repo info, or cleaning git references.

原文の言語: 英語

cargo-vendormod

A comprehensive tool for managing complex Rust workspaces, especially monorepos. It helps analyze dependency graphs, process crates in topological order, manage git submodules, and generate Nix flakes.

原文の言語: 英語

cargo-vendormod-tests

Run and extend the cargo-vendormod Rust test suite. Use when the user asks to run tests, add unit tests, check coverage, or debug test failures for cargo-vendormod.

原文の言語: 英語

cargo-vendormod-troubleshooting

Diagnose and recover from cargo-vendormod failures. Use when tests fail, builds error, zkperf errors, git submodules break, flakes are invalid, or LLM error pipelines misfire.

原文の言語: 英語

cargo-vendormod-vendoring

Git submodule vendoring workflow for cargo-vendormod. Use when initializing vendoring, fetching upstream, rebasing, managing releases, or patching .cargo/config.toml.

原文の言語: 英語

cargo-vendormod-whitespace-access

Strip, normalize, and sanitize untrusted text, file contents, command output, filenames, user-supplied input, and logs before writing them to disk or passing them downstream.

原文の言語: 英語

cargo-vendormod-workload

Collect repo info, build actions plans, run recursive workload vendoring, and generate workload reports. Use for workload processing and DASL workloads.

原文の言語: 英語

coordinator

Orchestrate multiple worktree agents. Spawn, monitor, communicate, and merge.

原文の言語: 英語

dag-cbor-restriction-morphisms

Build, test, and verify CBOR, DAG-CBOR, DRISL, IPLD, libipld, serde_ipld_dagcbor, rust-ipld-core, rust-ipld-dagpb, fuzz, and test-suite crates with cargo-vendormod. Use for dag-cbor workload management, flake coverage, encoding/decoding tests, fuzzing, and…

原文の言語: 英語

dotagents-providers-gemini

Deploy dotfiles for Gemini using the Gemini provider in dotagents. Use when configuring Gemini agent commands, skills, or instructions.

原文の言語: 英語

dotagents-providers-hermes

Deploy dotfiles for Hermes using the Hermes provider in dotagents. Use when configuring Hermes agent commands, skills, or instructions.

原文の言語: 英語

dotagents-providers-pi

Deploy dotfiles for Pi using the Pi provider in dotagents. Use when configuring Pi agent commands, skills, or instructions.

原文の言語: 英語

find-skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for…

原文の言語: 英語

git-submodule-cargo

Working with git submodules in cargo projects - initializing, updating, handling untracked content. Use when user encounters submodule issues in cargo workspaces.

原文の言語: 英語

gitnexus-cli

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\

原文の言語: 英語

gitnexus-debugging

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\

原文の言語: 英語

gitnexus-exploring

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\

原文の言語: 英語

gitnexus-guide

Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\

原文の言語: 英語

gitnexus-impact-analysis

Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\

原文の言語: 英語

gitnexus-pr-review

Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: \"Review this PR\", \"What does PR #42 change?\", \"Is this PR safe to merge?\

原文の言語: 英語

gitnexus-refactoring

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this class\", \"Move this to a separate file\

原文の言語: 英語

libipld-upgrade-consumers

Master the end-to-end workflow for discovering libipld consumer repos in the DASL codebase, adding them as targets to the libipld-upgrade harness, and setting up fuzz checking. Covers auto-discovery, git mirror management, target registration, fuzzing…

原文の言語: 英語

libipld-upgrade-fuzzing

Set up multi-engine fuzz checking for libipld consumer crates, modeled on the ipld-core fuzzing infrastructure. Covers Honggfuzz, AFL, libFuzzer, fuzzcheck-rs, Bolero, Ziggy, LibAFL, Siderophile, and TSFFS integration with Nix flakes.

原文の言語: 英語

libipld-upgrade

Master the libipld-upgrade harness for systematically upgrading Rust repositories from old libipld crates to a shim workspace. Use for patching dependencies, testing compatibility, and managing git mirror-based upgrade workflows.

原文の言語: 英語

merge

Commit, rebase, and merge the current branch.

原文の言語: 英語

nix-flakes

Creates reproducible builds, manages flake inputs, defines devShells, and builds packages with flake.nix. Use when initializing Nix projects, locking dependencies, or running nix build/develop commands.

原文の言語: 英語

nix

Comprehensive NixOS, Nix Flakes, Home Manager, and nix-darwin skill. Covers declarative system configuration, reproducible environments, package management, and cross-platform Nix workflows. Activate for any Nix/NixOS/Flakes/Home-Manager/nix-darwin tasks.

原文の言語: 英語

open-pr

Write a PR description using conversation context and open PR creation in browser.

原文の言語: 英語

openspec-apply-change

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

原文の言語: 英語

openspec-archive-change

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

原文の言語: 英語

openspec-continue-change

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

原文の言語: 英語

openspec-explore

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

原文の言語: 英語

openspec-new-change

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

原文の言語: 英語