self-test
Test Code Before Completion
Implementation work can finish with missed failures. This skill guides Claude, Codex, and Claude Code through tests, lint, and type checks before completion.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "self-test" from https://skillstore.io/skills/clouder0-self-test.md and its manifest at https://skillstore.io/api/skills/clouder0-self-test/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.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 "self-test". Check whether my new parser work is ready.
Expected outcome:
- Focused parser tests passed.
- Lint passed after one formatting fix.
- Type checks passed.
- The change is ready for review.
Using "self-test". Use the self-test loop while adding form validation.
Expected outcome:
- Added validation coverage for empty, invalid, and valid inputs.
- One test failed during implementation and was fixed.
- Final tests, lint, and type checks passed.
Using "self-test". Tell me if this task can be marked complete.
Expected outcome:
Not complete yet. The focused tests passed, but lint still reports issues that must be fixed first.
Security Audit
SafeThe external-command findings are false positives caused by Markdown code fences and example project commands, not executable skill code. The network-reconnaissance blocker is also a false positive; the cited line is a checklist item requiring tests to pass. No semantic prompt-injection or data-exfiltration evidence was found.
Risk Factors
⚙️ External commands (6)
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/clouder0-self-test/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/clouder0-self-test?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/clouder0-self-test?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/clouder0-self-test/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/clouder0-self-test.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
Clouder0. (2026). self-test security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/clouder0-self-test/audits/8BibTeX citation
@techreport{clouder0-clouder0-self-test-2026,
author = {Clouder0},
title = {self-test security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/clouder0-self-test/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: "self-test security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Clouder0"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/clouder0-self-test/audits/8"
identifiers:
- type: other
value: "skillstore:clouder0-self-test:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Verify a Feature Change
Run focused checks after implementing a feature, then fix failures before reporting completion.
Guide an AI Coding Session
Keep Claude, Codex, or Claude Code aligned with tests, lint, and type checks during implementation.
Standardize Quality Gates
Give contributors a clear pre-completion checklist for tests, lint, type checks, and console errors.
Try These Prompts
Use the self-test loop for my recent change. Run the relevant tests, lint, and type checks, then report any failures.
As you implement this feature, add or update tests for each changed behavior. Run focused checks before moving to the next part.
Use the self-test pattern to verify this bug fix. Confirm the failing case now passes and check nearby affected behavior.
Create a self-test plan for this repository. Identify focused checks, broader checks, lint, type checks, and the final completion criteria.
Best Practices
- Run focused checks after each meaningful code change.
- Use the repository's own documented commands when available.
- Report failing checks honestly and fix them before completion.
Avoid
- Declaring completion before tests, lint, and type checks run.
- Running only broad checks when a focused failing case exists.
- Ignoring warnings or console errors because tests passed.