verify
Verify Builds and Apply Review Fixes
Build failures and review fixes can slow delivery when errors are unclear. This skill runs focused verification workflows and guides safe recovery steps.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "verify" from https://skillstore.io/skills/chachamaru127-verify.md and its manifest at https://skillstore.io/api/skills/chachamaru127-verify/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "verify". Verify my recent changes before review.
Expected outcome:
Build passed. Type checks passed. Tests passed. Lint reported one warning that should be reviewed before merge.
Using "verify". The unit tests are failing after my change.
Expected outcome:
The failure appears related to outdated expectations. I recommend confirming the expected behavior before changing the test.
Using "verify". Apply the approved review fixes.
Expected outcome:
Three safe fixes were applied. One behavior-sensitive item was skipped and needs manual confirmation.
Security Audit
High RiskMost static command and entropy findings are false positives caused by Markdown backticks, fenced examples, Japanese documentation, and readable tables. The real concerns are a prompt-priority override sentence in SKILL.md and the intended use of Bash to run project-controlled build and test scripts.
Confirmed security concerns (2)
Risk Factors
⚙️ External commands (44)
📁 Filesystem access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/chachamaru127-verify/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/chachamaru127-verify?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/chachamaru127-verify?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/chachamaru127-verify/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/chachamaru127-verify.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Chachamaru127. (2026). verify security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/chachamaru127-verify/audits/8BibTeX citation
@techreport{chachamaru127-chachamaru127-verify-2026,
author = {Chachamaru127},
title = {verify security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/chachamaru127-verify/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "verify security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Chachamaru127"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/chachamaru127-verify/audits/8"
identifiers:
- type: other
value: "skillstore:chachamaru127-verify:audit:8"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
react-verify
2026-10-03
chachamaru127-verify
2026-09-09
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Verify a completed change
Run build, type-check, test, and lint checks before sending code for review.
Recover from failing tests
Analyze failure output, identify likely causes, and apply small fixes with verification.
Apply approved review feedback
Convert review findings into safe fixes, then present the result and next checks.
Try These Prompts
Verify my recent changes. Check build, tests, type checks, and lint. Summarize any failures and the next action.
The tests are failing. Read the failure output, identify the cause, propose a safe fix, and rerun the relevant checks.
Combine these review findings into one prioritized summary. Separate security, performance, quality, and accessibility issues.
Apply only the review fixes I approved. Show the changed files, explain skipped items, and verify the result afterward.
Best Practices
- Review commands before execution when working in unfamiliar repositories.
- Ask for approval before changing tests, lint settings, CI settings, or expected values.
- Rerun the smallest relevant verification command after each fix.
Avoid
- Do not skip tests to make a verification run pass.
- Do not weaken lint, type, or CI rules without explicit approval.
- Do not apply review fixes that change behavior without understanding the requirement.