audit
Audit Code Quality and Technical Debt
Codebases can hide TODOs, deprecated APIs, type gaps, and architecture drift. This skill guides a systematic audit and produces a structured report.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "audit" from https://skillstore.io/skills/cygnusfear-audit.md and its manifest at https://skillstore.io/api/skills/cygnusfear-audit/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 "audit". Audit the frontend package before release.
Expected outcome:
The report lists files reviewed, issue counts by severity, top findings, type check results, and lint findings.
Using "audit". Find technical debt in the services folder.
Expected outcome:
The audit groups findings by deprecations, TODOs, architecture issues, type issues, and code smells.
Using "audit". Review this repository for onboarding risks.
Expected outcome:
The summary highlights repeated patterns, naming inconsistencies, high-risk modules, and areas needing maintainer review.
Security Audit
SafeNo prompt injection, data exfiltration, or malicious intent was found in SKILL.md. Three static detections are markdown-only false positives. Two detections are real external-command guidance for local validation tools.
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (5)
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/cygnusfear-audit/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cygnusfear-audit?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cygnusfear-audit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cygnusfear-audit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cygnusfear-audit.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
Cygnusfear. (2026). audit security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cygnusfear-audit/audits/10BibTeX citation
@techreport{cygnusfear-cygnusfear-audit-2026,
author = {Cygnusfear},
title = {audit security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/cygnusfear-audit/audits/10},
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: "audit security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "Cygnusfear"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/cygnusfear-audit/audits/10"
identifiers:
- type: other
value: "skillstore:cygnusfear-audit:audit:10"
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
pbakaus-audit
2026-08-21
cygnusfear-audit
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Pre-release Quality Review
Run a structured review before a release to find type risks, stale work, and maintainability issues.
Technical Debt Inventory
Create a grouped list of debt, code smells, and architecture concerns for planning work.
Repository Onboarding Audit
Map common quality issues and conventions before contributing to an unfamiliar codebase.
Try These Prompts
Audit this repository for TODOs, deprecated code, type issues, architecture problems, and code smells. Create a structured report.
Audit the selected package only. Focus on maintainability, type safety, duplication, and architectural consistency.
Audit the release branch. Run configured type and lint checks after confirming the commands with me.
Audit cross-file architecture risks. Identify coupling, circular dependencies, inconsistent patterns, and systemic technical debt.
Best Practices
- Confirm the audit scope before starting a large repository review.
- Approve any local commands before the skill runs project tooling.
- Review the final report with maintainers before creating tickets.
Avoid
- Do not use it as a replacement for security testing.
- Do not run project scripts from an untrusted repository without approval.
- Do not treat every reported smell as equally urgent.
Frequently Asked Questions
Does this skill change source files?
Can it run automated checks?
Should I approve commands first?
What languages does it support?
Does it prioritize fixes?
Can Claude, Codex, and Claude Code use it?
Developer Details
Author
CygnusfearLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
26421118b848d9f1efc0aa169d8a7a9e7e0a877e
Maintenance freshness
7/18/2026
Usage
5 downloads · 207 views
File structure
📄 SKILL.md