Skip to content

aiskillstore/marketplace / skills/5t111111/code-conventions

code-conventions

Verified

Guide for code conventions and formatting

FileKindSize
SKILL.mdskill md468 B
skill-report.jsonconfig8.2 KB

skill-report.json

View on GitHub
{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-07-04T16:57:23.285Z",
    "slug": "5t111111-code-conventions",
    "source_url": "https://github.com/5t111111/tailwind-theme-figma-variables/tree/main/.github/skills/code-conventions",
    "source_ref": "main",
    "model": "codex",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "ba69f41bfb7e801924ed26c61690fe108e6b5f8fa6a5e8e87dec3e36f15ba362",
    "tree_hash": "e61e830ced654a9cb65afbec99e53ae899cfeff54b1a475973456cd819fd87d3",
    "provenance": {
      "model_effective": "codex",
      "fallback_chain": [
        {
          "agent": "codex",
          "outcome": "success"
        }
      ],
      "analysis_version": "3.0.0"
    }
  },
  "skill": {
    "name": "code-conventions",
    "description": "Guides AI coding assistants to follow Deno formatting and documentation conventions.",
    "summary": "Apply Deno formatting and English JSDoc or TSDoc documentation rules.",
    "icon": "📦",
    "version": "1.0.1",
    "author": "5t111111",
    "license": "MIT",
    "category": "coding",
    "tags": [
      "deno",
      "formatting",
      "documentation",
      "jsdoc",
      "tsdoc"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": [
      "external_commands"
    ]
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "analysis_status": "ok",
    "summary": "The 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.",
    "remediation": [],
    "risk_factor_evidence": [
      {
        "factor": "external_commands",
        "evidence": [
          {
            "file": "SKILL.md",
            "line_start": 13,
            "line_end": 13
          }
        ]
      }
    ],
    "static_findings": [
      {
        "id": "external_commands:SKILL.md:13:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 13,
        "line_end": 13,
        "snippet": "- Always run `mise run fmt` to format the code before committing"
      }
    ],
    "finding_verdicts": [
      {
        "id": "external_commands:SKILL.md:13:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "SKILL.md line 13 uses backticks as Markdown inline code around the formatter command. There is no executable script, interpolation, or shell backtick execution in the skill file."
      }
    ],
    "semantic_findings": [],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 1,
    "total_lines": 20,
    "audit_model": "codex",
    "audited_at": "2026-07-04T16:57:23.285Z",
    "agent_auto_install_policy": "allowed",
    "manual_install_policy": "allowed"
  },
  "content": {
    "user_title": "Apply Deno Code Conventions",
    "value_statement": "Teams lose consistency when Deno formatting and documentation rules are unclear. This skill guides agents to format with mise and document symbols in English.",
    "seo_keywords": [
      "Claude",
      "Codex",
      "Claude Code",
      "Deno formatting",
      "code conventions",
      "JSDoc",
      "TSDoc",
      "mise run fmt",
      "AI coding assistant",
      "documentation standards"
    ],
    "actual_capabilities": [
      "Guides agents to run mise run fmt before commits.",
      "Applies Deno-oriented code formatting expectations.",
      "Requires documentation comments for functions, classes, and properties.",
      "Requests English documentation comments.",
      "Provides concise repository convention guidance from one skill file."
    ],
    "limitations": [
      "Does not include automated formatter code.",
      "Does not define lint rules beyond formatting and documentation.",
      "Assumes the repository has a mise fmt task configured.",
      "Does not cover testing, release, or architecture conventions."
    ],
    "use_cases": [
      {
        "title": "Standardize Deno Repositories",
        "description": "Apply shared formatting and documentation expectations during routine code changes.",
        "target_user": "Repository maintainers"
      },
      {
        "title": "Prepare Pull Requests",
        "description": "Check that changed symbols have English documentation before a review.",
        "target_user": "Application developers"
      },
      {
        "title": "Guide AI Coding Sessions",
        "description": "Give Claude, Codex, or Claude Code concise rules for consistent edits.",
        "target_user": "AI-assisted teams"
      }
    ],
    "prompt_templates": [
      {
        "title": "Check Basic Formatting",
        "prompt": "Apply the code conventions to my current Deno changes. Focus on formatting and documentation comments.",
        "scenario": "Beginner check before a small commit"
      },
      {
        "title": "Prepare a Commit",
        "prompt": "Review this change against the code conventions. Format the project if appropriate and report any missing documentation.",
        "scenario": "Routine pre-commit review"
      },
      {
        "title": "Review Public Symbols",
        "prompt": "Inspect the changed functions, classes, and properties. Ensure each one has clear English JSDoc or TSDoc comments.",
        "scenario": "Documentation-focused review"
      },
      {
        "title": "Audit a Pull Request",
        "prompt": "Audit this pull request against the code conventions. Separate formatting issues, missing documentation, and assumptions about project tooling.",
        "scenario": "Advanced review across multiple files"
      }
    ],
    "output_examples": [
      {
        "input": "Review my Deno change before commit.",
        "output": "Formatting was checked against the project formatter. One exported function needs an English documentation comment before review."
      },
      {
        "input": "Check whether the new class follows the conventions.",
        "output": "The class needs a TSDoc comment. Its public property also needs documentation in English."
      },
      {
        "input": "Prepare this branch for review.",
        "output": "The branch follows the documented conventions after formatting. No missing function, class, or property comments were found."
      }
    ],
    "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."
    ],
    "anti_patterns": [
      "Skipping formatting because the change looks small.",
      "Adding undocumented public functions, classes, or properties.",
      "Writing documentation comments in a language other than English."
    ],
    "faq": [
      {
        "question": "Does this skill run code by itself?",
        "answer": "No. It provides instructions for an AI assistant. The assistant may run the formatter during a coding task."
      },
      {
        "question": "Which projects does it fit best?",
        "answer": "It fits Deno projects that use mise for formatting and require JSDoc or TSDoc comments."
      },
      {
        "question": "Can I use it with Claude Code?",
        "answer": "Yes. It supports Claude, Codex, and Claude Code for AI-assisted repository work."
      },
      {
        "question": "Does it replace a linter?",
        "answer": "No. It gives convention guidance and does not define a full lint rule set."
      },
      {
        "question": "What documentation does it require?",
        "answer": "It requires comments for functions, classes, and properties. The comments should be written in English."
      },
      {
        "question": "What should I check before using the formatter command?",
        "answer": "Check that the repository defines the mise formatter task and that you trust the project scripts."
      }
    ]
  },
  "file_structure": [
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 20
    }
  ]
}
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall