analyze — community analyze, eshop-demo, community, ide skills

v1.0.0
GitHub

À propos de ce Skill

Parfait pour les agents de revue de code nécessitant des capacités d'analyse de microservices .NET avancées. Run code analyzers (unused packages, code quality, security). Use when user wants to analyze the codebase or runs /analyze.

cooper538 cooper538
[0]
[0]
Updated: 2/13/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 9/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
9/11
Quality Score
54
Canonical Locale
en
Detected Body Locale
en

Parfait pour les agents de revue de code nécessitant des capacités d'analyse de microservices .NET avancées. Run code analyzers (unused packages, code quality, security). Use when user wants to analyze the codebase or runs /analyze.

Pourquoi utiliser cette compétence

Permet aux agents de détecter les packages NuGet inutilisés, les problèmes de qualité de code et les vulnérabilités de sécurité en utilisant dotnet-unused et les avertissements de Roslyn, améliorant ainsi la sécurité et la maintenabilité globales de la base de code.

Meilleur pour

Parfait pour les agents de revue de code nécessitant des capacités d'analyse de microservices .NET avancées.

↓ Cas d'utilisation exploitables for analyze

Détection des packages NuGet inutilisés pour optimiser les dépendances
Analyse des vulnérabilités de sécurité pour assurer l'intégrité de la base de code
Analyse de la qualité du code pour améliorer le respect des normes de codage

! Sécurité et Limitations

  • Les bases de code d'architecture de microservices .NET uniquement
  • Nécessite des outils d'analyseur spécifiques comme dotnet-unused

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is analyze?

Parfait pour les agents de revue de code nécessitant des capacités d'analyse de microservices .NET avancées. Run code analyzers (unused packages, code quality, security). Use when user wants to analyze the codebase or runs /analyze.

How do I install analyze?

Run the command: npx killer-skills add cooper538/eshop-demo/analyze. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for analyze?

Key use cases include: Détection des packages NuGet inutilisés pour optimiser les dépendances, Analyse des vulnérabilités de sécurité pour assurer l'intégrité de la base de code, Analyse de la qualité du code pour améliorer le respect des normes de codage.

Which IDEs are compatible with analyze?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for analyze?

Les bases de code d'architecture de microservices .NET uniquement. Nécessite des outils d'analyseur spécifiques comme dotnet-unused.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add cooper538/eshop-demo/analyze. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use analyze immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

analyze

Install analyze, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Code Analyzer

Run analysis tools on the codebase.

Usage

/analyze              # Run all analyzers
/analyze packages     # Unused NuGet packages only
/analyze quality      # Code quality only
/analyze security     # Security vulnerabilities only

Arguments

  • $ARGUMENTS - Analyzer type to run
    • Empty or all - Run all analyzers
    • packages - Detect unused NuGet packages (dotnet-unused)
    • quality - Check code style and Roslyn warnings
    • security - Scan for known CVEs and deprecated packages

Process

Step 1: Ensure Tools Are Installed

Run dotnet tool restore if tools are not available.

Step 2: Execute Analyzer(s)

Based on $ARGUMENTS:

ArgumentScript
(empty) / all./tools/analyzers/run-all.sh
packages./tools/analyzers/unused-packages/analyze.sh
quality./tools/analyzers/code-quality/analyze.sh
security./tools/analyzers/security/analyze.sh

Step 3: Report Results

Summarize findings:

  • Number of issues found per category
  • Actionable recommendations

Output Format

=== Analysis Results ===

Unused Packages: X issues
  - ProjectName: PackageName

Code Quality: X warnings
  - File:Line - Warning description

Security: X vulnerabilities
  - PackageName - CVE-XXXX-XXXXX (severity)

Recommendations:
  1. Remove unused package X from project Y
  2. Fix warning Z in file W

Compétences associées

Looking for an alternative to analyze or another community skill for your workflow? Explore these related open-source skills.

Voir tout

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
Intelligence artificielle

widget-generator

Logo of f
f

Générez des plugins de widgets personnalisables pour le système de flux prompts.chat

★ 149.6k
⑂ 0
Intelligence artificielle

flags

Logo of vercel
vercel

Le Cadre de Réaction

★ 138.4k
⑂ 0
Navigateur

pr-review

Logo of pytorch
pytorch

Tenseurs et réseaux neuronaux dynamiques en Python avec une forte accélération GPU

★ 98.6k
⑂ 0
Développeur