Skip to content
cccskills
FreePublished on GitHub

daily-coding

Use for everyday coding tasks that involve writing or modifying source code.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Daily Coding Checklist

A minimal coding quality assurance checklist ensuring every code modification follows best practices.

When to Use

Use this skill for:

  • Implementing new features
  • Adding code or modifying existing code
  • User requests like "write a...", "implement...", "add...", or "modify..."
  • Any coding task that involves Edit or Write tools

When Not to Use

Do not use this skill for:

  • Pure reading or understanding tasks with no modification intent
  • Work already covered by specialized skills such as bug-detective, architecture-design, or verification-loop
  • Configuration-only changes
  • Documentation-only writing

Core Checklist

Before Starting

  • Read before modify - Must read target file with Read tool before making changes
  • Understand context - Confirm understanding of existing code logic and design intent

During Coding

  • Minimal changes - Only change what's necessary, no over-engineering, no unrelated features
  • Type safety - Add type hints for Python, avoid any in TypeScript
  • Security check - Avoid command injection, XSS, SQL injection vulnerabilities

After Completion

  • Verify execution - Ensure code runs correctly with no syntax errors
  • Clean up - Remove print/console.log debug statements and temporary files
  • Brief summary - Inform user what was changed and the scope of impact

Quick Reference

Common Mistakes to Avoid

# ❌ Don't
def process(data=[]):  # Mutable default argument
    pass

# ✅ Should
def process(data: list | None = None):
    data = data or []
# ❌ Don't
except:  # Bare except
    pass

# ✅ Should
except ValueError as e:
    logger.error(f"Processing failed: {e}")
    raise

Security Check Points

  • User input must be validated/escaped
  • Use pathlib for file paths, avoid path traversal
  • Never hardcode sensitive info (API keys, passwords)

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when creating or configuring Claude Code agents and their frontmatter.

The English summary is being prepared. Showing the original description.

Galaxy-Dawn/claude-scholar5.8KUpdated Sep 23, 2026

Use only when creating new registrable ML components that require Factory or Registry patterns.

The English summary is being prepared. Showing the original description.

Galaxy-Dawn/claude-scholar5.8KUpdated Sep 23, 2026

This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem", "something is broken", "this isn't working", "why is this failing", or reports errors/exceptions/bugs. Provides systematic debugging workflow and common error patterns.

The English summary is being prepared. Showing the original description.

Galaxy-Dawn/claude-scholar5.8KUpdated Sep 23, 2026

This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed verification principles and common error patterns.

The English summary is being prepared. Showing the original description.

Galaxy-Dawn/claude-scholar5.8KUpdated Sep 23, 2026

This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.

The English summary is being prepared. Showing the original description.

Galaxy-Dawn/claude-scholar5.8KUpdated Sep 23, 2026

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

The English summary is being prepared. Showing the original description.

Galaxy-Dawn/claude-scholar5.8KUpdated Sep 23, 2026

See all skills by Galaxy-Dawn

Report a problem with this skill