rewriting-code-comments

Refactor Objective-C code comments into Apple HeaderDoc standards.

Updated Jul 26, 2026

Search Tags:#documentation #refactoring #code comments #objective-c #headerdoc #llm-isms

Ready to run

npx skills add https://github.com/jvalinsky/garazyk --skill rewriting-code-comments

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rewriting-code-comments
Source: https://github.com/jvalinsky/garazyk/tree/main/.opencode/skills/rewriting-code-comments
Command: npx skills add https://github.com/jvalinsky/garazyk --skill rewriting-code-comments

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms informal, AI-generated, or conversational code comments and documentation into professional, standards-compliant Apple HeaderDoc, ensuring clarity and maintainability.

Core Features & Use Cases

LLM-ism Removal: Eliminates conversational patterns, marketing jargon, and emojis from comments.
HeaderDoc Compliance: Enforces Apple's HeaderDoc standards for Objective-C, improving Xcode Quick Help integration.
Use Case: Refactor a codebase where comments were auto-generated by an LLM, making them professional, accurate, and easy for developers to understand within Xcode.

Quick Start

Use the rewriting code comments skill to convert the provided Objective-C method documentation to Apple HeaderDoc standards.

Frequently Asked Questions about rewriting-code-comments

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

FAQPage Schema

How do I convert AI-generated Objective-C comments into Apple HeaderDoc format?▼

To convert AI-generated Objective-C comments into Apple HeaderDoc format, you need to refactor the text by removing conversational patterns, marketing language, and emojis. This process transforms informal documentation into structured professional technical standards.

What is the best way to remove LLM-isms and conversational patterns from code comments?▼

Removing LLM-isms from code comments involves stripping conversational patterns, marketing jargon, and emojis from the documentation. This refactoring process enforces Apple HeaderDoc standards to ensure technical accuracy and professional structure.

How do I make my Objective-C code comments compatible with Xcode Quick Help?▼

Making Objective-C code comments compatible with Xcode Quick Help requires enforcing Apple HeaderDoc standards. By refactoring informal or AI-generated text into structured technical documentation, the comments integrate seamlessly with Xcode's help features.

Does this refactoring process support codebases with auto-generated LLM documentation?▼

Yes, this refactoring process supports codebases with auto-generated LLM documentation by eliminating self-reflection and marketing language. It focuses on transforming informal AI-generated text into professional, accurate documentation for Objective-C environments.

Why should I refactor informal Objective-C documentation to Apple HeaderDoc standards?▼

Refactoring informal Objective-C documentation to Apple HeaderDoc standards ensures clarity and maintainability. It removes conversational patterns and emojis, guaranteeing technical accuracy while providing structured documentation compatible with Xcode Quick Help.

What are the limitations of using HeaderDoc standards for Objective-C code comments?▼

A limitation of using HeaderDoc standards for Objective-C code comments is that the refactoring process specifically targets Apple's documentation format. It focuses on removing LLM-isms and informal text, meaning it is highly specialized for Objective-C rather than general programming languages.