code-conventions
Apply Deno Code Conventions
Teams lose consistency when Deno formatting and documentation rules are unclear. This skill guides agents to format with mise and document symbols in English.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "code-conventions" from https://skillstore.io/skills/5t111111-code-conventions.md and its manifest at https://skillstore.io/api/skills/5t111111-code-conventions/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 "code-conventions". Review my Deno change before commit.
Expected outcome:
Formatting was checked against the project formatter. One exported function needs an English documentation comment before review.
Using "code-conventions". Check whether the new class follows the conventions.
Expected outcome:
The class needs a TSDoc comment. Its public property also needs documentation in English.
Using "code-conventions". Prepare this branch for review.
Expected outcome:
The branch follows the documented conventions after formatting. No missing function, class, or property comments were found.
Security Audit
SafeThe static finding is a false positive. SKILL.md line 13 contains a Markdown inline command reference for a formatter, not executable Ruby or shell backtick syntax.
Risk Factors
⚙️ External commands (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/5t111111-code-conventions/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/5t111111-code-conventions?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/5t111111-code-conventions?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/5t111111-code-conventions/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/5t111111-code-conventions.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
5t111111. (2026). code-conventions security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/5t111111-code-conventions/audits/8BibTeX citation
@techreport{5t111111-5t111111-code-conventions-2026,
author = {5t111111},
title = {code-conventions security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/5t111111-code-conventions/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: "code-conventions security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "5t111111"
date-released: "2026-07-04"
url: "https://skillstore.io/skills/5t111111-code-conventions/audits/8"
identifiers:
- type: other
value: "skillstore:5t111111-code-conventions:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Standardize Deno Repositories
Apply shared formatting and documentation expectations during routine code changes.
Prepare Pull Requests
Check that changed symbols have English documentation before a review.
Guide AI Coding Sessions
Give Claude, Codex, or Claude Code concise rules for consistent edits.
Try These Prompts
Apply the code conventions to my current Deno changes. Focus on formatting and documentation comments.
Review this change against the code conventions. Format the project if appropriate and report any missing documentation.
Inspect the changed functions, classes, and properties. Ensure each one has clear English JSDoc or TSDoc comments.
Audit this pull request against the code conventions. Separate formatting issues, missing documentation, and assumptions about project tooling.
Best Practices
- Confirm mise and Deno are installed before relying on formatting output.
- Ask for permission before running formatter commands in unfamiliar repositories.
- Review exported symbols for missing JSDoc or TSDoc comments.
Avoid
- Skipping formatting because the change looks small.
- Adding undocumented public functions, classes, or properties.
- Writing documentation comments in a language other than English.
Frequently Asked Questions
Does this skill run code by itself?
Which projects does it fit best?
Can I use it with Claude Code?
Does it replace a linter?
What documentation does it require?
What should I check before using the formatter command?
Developer Details
Author
5t111111License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/5t111111/tailwind-theme-figma-variables/tree/main/.github/skills/code-conventionsRef
e9e4712298ed071d92417a41714be123eb8364fa
Maintenance freshness
7/18/2026
Usage
17 downloads · 177 views
File structure
📄 SKILL.md