Agent skill
daily-coding
Use for everyday coding tasks that involve writing or modifying source code.
Install this agent skill to your Project
npx add-skill https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/daily-coding
SKILL.md
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, ortdd-guide - 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
anyin 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)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
bug-detective
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.
doc-coauthoring
This skill should be used when the user asks to co-author documentation, draft a proposal, write a technical spec, create a decision doc or RFC, or structure a substantial document through iterative collaboration and reader testing.
daily-paper-generator
Use when the user asks to "generate daily paper", "search arXiv for EEG papers", "find EEG decoding papers", "review brain-computer interface papers", or wants to create paper summaries for EEG/brain decoding/speech decoding research. This skill automates searching arXiv for recent papers on EEG decoding, EEG speech decoding, or brain foundation models, reviewing paper quality, and generating structured Chinese/English summaries.
paper-self-review
This skill should be used when the user asks to "review paper quality", "check paper completeness", "validate paper structure", "self-review before submission", or mentions systematic paper quality checking. Provides comprehensive quality assurance checklist for academic papers.
agent-identifier
Use when creating or configuring Claude Code agents and their frontmatter.
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
Didn't find tool you were looking for?