원클릭으로 Manus에서 모든 스킬 실행

apiiro-fix

스타0

포크1

업데이트2026년 4월 26일 11:02

Apiiro CLI commands for remediating and fixing security risks: get remediation prompts and use Guardian AI to fix findings. Use this skill whenever the user wants to fix, remediate, patch, or resolve a security risk or vulnerability in their repository. Also trigger when they ask "how do I fix this risk", "remediate this finding", "resolve this vulnerability", or want actionable guidance on resolving a security issue. For listing or inspecting risks, use the apiiro-risks skill instead.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

apiiro

apiiro/marketplace

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Apiiro Fix

Remediate security risks via the Apiiro CLI. The workflow tries automated remediation first, then falls back to Guardian AI for guidance.

Workflow

Get the risk ID — use apiiro risks or apiiro risks get <id> to identify the risk (see apiiro-risks skill).
Try automated remediation — run apiiro risks remediate <risk-id>.
- If the response has is_prompt: true, the content is an actionable fix prompt — apply it directly.
- If is_prompt: false, automated remediation isn't available for this risk category — proceed to step 3.

Fall back to Guardian — ask Guardian for advice:

apiiro guardian query "how do I remediate risk <risk-id>?" --timeout 120

Apply the fix — use the returned prompt or Guardian's guidance to make code changes.

Options

-o, --output <json|text>, -f, --file <path>, --no-color.

이 저장소의 다른 Skills

같은 저장소

apiiro-setup

apiiro/marketplace

Install Apiiro CLI, authenticate, verify version, check available features, and configure hooks

2026-06-090

apiiro-diff-scan

apiiro/marketplace

Apiiro CLI command for comparing two git references for security risks — the primary CI/CD integration point. Use this skill whenever the user mentions diff scanning, comparing branches or commits for security issues, CI/CD security gates, blocking PRs on risk, or wants to wire Apiiro into a build pipeline. Even if the user doesn't say "apiiro", trigger when they say things like "scan this PR", "compare main to my branch for security", "block merges on critical risks", or want to set up security gating in CI. For local secrets/OSS scanning, use apiiro-fast-scan instead.

2026-05-140

apiiro-secure-prompt

apiiro/marketplace

Apiiro CLI command for enhancing developer prompts with security considerations before coding begins. Takes a coding task description and returns the same task with security requirements injected — preserving the original business intent while adding security guardrails. Use this skill whenever the user wants to improve a coding task with security guidance, add security requirements to a task before starting implementation, or get a security-enhanced version of a prompt. Trigger on phrases like "make this prompt more secure", "add security to my task", "what security should I consider for this feature", or when the user is about to start a coding task and wants security baked in. This is different from threat-model (which produces a full STRIDE analysis report) — secure-prompt enhances a *task description* the user is about to implement.

2026-04-290

apiiro-fast-scan

apiiro/marketplace

Apiiro CLI command for quick local security scanning: fast-scan for secrets and OSS vulnerabilities, plus pre-commit hooks. Use this skill whenever the user mentions scanning code locally, secrets detection, OSS vulnerabilities, pre-commit hooks, or wants to check files for security issues before committing. Even if the user doesn't say "apiiro", trigger when they say things like "scan for secrets", "check my code before I push", "are there any leaked credentials", "check dependencies for vulnerabilities", or want to set up local security scanning. For comparing git references in CI/CD, use apiiro-diff-scan instead.

2026-04-260

apiiro-guardian

apiiro/marketplace

Apiiro CLI commands for querying the Guardian AI agent: ask security questions, get analysis and insights about a repository, and manage repository detection. Use this skill whenever the user wants AI-powered security analysis, security posture review, or wants to ask questions about their codebase's security. Also trigger when they need deep analysis of authentication flows, attack surfaces, or want an AI to explain security concepts. Even without mentioning "apiiro" or "guardian", trigger when the user asks things like "is this code secure?", "what's the attack surface here?", or "explain this vulnerability". For dedicated STRIDE threat modeling of a design or feature spec, use the apiiro-threat-model skill instead. For fixing a known risk, use apiiro-fix.

2026-04-260

apiiro-risks

apiiro/marketplace

Apiiro CLI commands for viewing and inspecting risks in a repository: list, filter, and get details on known risks. Use this skill whenever the user asks about security risks, vulnerabilities, or findings in their repository. Also trigger when they want to list, filter, or investigate risks by category or severity. Even without mentioning "apiiro", trigger when the user asks things like "what risks does this repo have", "any vulnerabilities here?", "show me the security findings", or "what's the risk level of this project". For fixing or remediating risks, use the apiiro-fix skill instead.

2026-04-260

name

apiiro-fix

description

Apiiro Fix

Remediate security risks via the Apiiro CLI. The workflow tries automated remediation first, then falls back to Guardian AI for guidance.

Workflow

Get the risk ID — use apiiro risks or apiiro risks get <id> to identify the risk (see apiiro-risks skill).
Try automated remediation — run apiiro risks remediate <risk-id>.
- If the response has is_prompt: true, the content is an actionable fix prompt — apply it directly.
- If is_prompt: false, automated remediation isn't available for this risk category — proceed to step 3.

Fall back to Guardian — ask Guardian for advice:

apiiro guardian query "how do I remediate risk <risk-id>?" --timeout 120

Apply the fix — use the returned prompt or Guardian's guidance to make code changes.

Options

-o, --output <json|text>, -f, --file <path>, --no-color.