cl-coding-style

Standardize Common Lisp naming, indentation, and docstring conventions.

1|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/cxxxr/.claude --skill cl-coding-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cl-coding-style
Source: https://github.com/cxxxr/.claude/tree/main/skills/cl-coding-style
Command: npx skills add https://github.com/cxxxr/.claude --skill cl-coding-style

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Common Lisp コードの一貫性と可読性を高め、コードレビューの負荷を軽減します。

Core Features & Use Cases

  • 命名規則の適用: 関数・変数の命名規則、述語名、変換関数の命名を統一
  • インデントとフォーマット: 2スペースインデント、括弧配置の統一
  • パッケージ設計: defpackage の推奨スタイル、import-from vs use の使い分け
  • ドキュメント: Docstring の標準化、クラスと関数の目的説明

Quick Start

Google Common Lisp Style Guide を参照し、既存コードベースに対して命名・フォーマットの規約を適用します(references ディレクトリを参照)。

Frequently Asked Questions about cl-coding-style

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Common Lisp code formatting and naming conventions across my project?

Apply Common Lisp coding standards by enforcing 2-space indentation, kebab-case naming for functions and variables, -p suffixes for predicates, *earmuffs* for dynamic variables, +plus-signs+ for constants, and maintaining 100-120 character line length. This Skill implements these conventions during development and code review to ensure consistency.

What are Common Lisp naming conventions for functions, variables, and special types?

Common Lisp naming conventions include kebab-case for functions and variables, -p suffixes for predicates, foo->bar format for conversion functions, *earmuffs* surrounding dynamic variables, and +plus-signs+ wrapping constants. These conventions improve code readability and make intent explicit across codebases.

How should I structure defpackage and decide between import-from and use?

Defpackage design involves choosing between import-from for explicit symbol imports and use for inheriting all exported symbols from a package. This Skill applies Google Common Lisp Style Guide recommendations to standardize package organization, reducing ambiguity and improving maintainability during development.

What docstring standards should I follow for Common Lisp classes and functions?

Standardize docstrings by documenting class and function purpose explicitly, following consistent formatting and placement conventions. This Skill enforces docstring standards alongside naming and formatting rules to reduce code review overhead and improve code clarity.

Can I apply Common Lisp style conventions during code review and refactoring?

Yes. This Skill applies coding standards during development, review, and refactoring phases to guide naming, indentation, package usage, and docstrings. It standardizes style across existing codebases while maintaining consistency with Google Common Lisp Style Guide principles.

Does this work with existing Common Lisp codebases, or only new projects?

This Skill applies to both new and existing Common Lisp codebases. It standardizes formatting and naming conventions across projects during active development, review cycles, and refactoring work without requiring project restructuring.