Scan a cloned repository for tech stack, CI/CD, security, and test coverage gaps.
npx skills add https://github.com/kagenti/kagenti --skill orchestrate-scan
Please help me install this Agent Skill. Skill: orchestrate:scan Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/orchestrate%3Ascan Command: npx skills add https://github.com/kagenti/kagenti --skill orchestrate-scan
This Skill automates the comprehensive assessment of a target software repository's health, identifying gaps in CI/CD maturity, security posture, test coverage, and supply chain robustness.
Scan the repository located at .repos/my-target-repo to assess its current state.
High-intent search queries and answers about installing and using this skill.
Assessing code quality and CI/CD maturity involves scanning a target repository to evaluate its tech stack, CI status, action pinning, test coverage, and supply chain health. The scan identifies specific gaps and recommends subsequent orchestration phases to improve overall repository health.
The best way to identify gaps in test coverage and security posture before refactoring is to run an automated repository assessment. This evaluates backend, UI, E2E, and infra test coverage alongside security scanning and governance, providing an actionable report of the current state.
To check supply chain health and dependency management, scan the cloned repository to assess dependency pinning and overall robustness. The assessment pinpoints specific areas needing improvement, such as unpinned dependencies or inadequate security scanning coverage.
The repository scan requires a specific directory structure, expecting the target software repository to be cloned locally into the `.repos/<target>/` directory. This setup is necessary for the assessment scripts to access and analyze the codebase effectively.
Yes, you can automate security assessment and test coverage analysis by running a comprehensive repository scan. This automates the evaluation of security scanning coverage, governance, and backend to infrastructure test coverage, generating a clear report of actionable gaps.
When scanning a repository for technology stack and CI status, the assessment is limited to analyzing the statically cloned codebase in the `.repos/` directory. It evaluates existing configurations and code but does not execute pipelines or dynamically test running infrastructure.
kagentiClone a repository into `.repos/` and apply Kagenti conventions.
dogearedAudit code, dependencies, CI/CD, and infrastructure to generate a Security Posture Report.
Ramprasad4121Identify software dependencies with elevated exploitation or takeover risks via GitHub data.
eliottbusinessAutomate pre-commit code review with static analysis and security scanning.
