CtrlK
BlogDocsLog inGet started
Tessl Logo

remove-llm-comments

Remove unnecessary LLM-generated comments from code

57

Quality

66%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/remove-llm-comments/SKILL.md
SKILL.md
Quality
Evals
Security

Remove LLM comments

LLMs leave behind comments that no human would write. They clutter the code and make it obvious an AI wrote it.

What to remove

Obvious narration

// Create a new vector to store results
let results = Vec::new();

// Iterate over items
for item in items {

The code already says what it does. Delete these.

Changelog-style comments

# Added error handling for edge cases
# Updated to use new API
# Fixed bug where X would fail

That's what git history is for.

Section markers that add nothing

// ============================================
// HELPER FUNCTIONS
// ============================================

If you need these, the file is too long. Split it.

Filler explanations

// This function takes a user ID and returns the user object
function getUser(userId: string): User {

The signature already tells you this.

What to keep

  • Comments explaining why, not what (business logic, non-obvious constraints)
  • Links to issues, specs, or external docs
  • Warnings about gotchas or edge cases
  • License headers
  • Doc comments for public APIs

Example

Before:

// Import the necessary modules for HTTP handling
use axum::{Router, routing::get};

// Create the main application router
// This router will handle all incoming HTTP requests
fn create_router() -> Router {
    // Build the router with a health check endpoint
    Router::new()
        // Add a GET route for the health check
        .route("/health", get(health_check))
}

// Health check handler function
// Returns a simple OK response to indicate the service is running
async fn health_check() -> &'static str {
    "ok"
}

After:

use axum::{Router, routing::get};

fn create_router() -> Router {
    Router::new()
        .route("/health", get(health_check))
}

async fn health_check() -> &'static str {
    "ok"
}
Repository
gitlabhq/orbit-knowledge-graph
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.