
Daily Coding
- 248 installs
- 5k repo stars
- Updated July 17, 2026
- galaxy-dawn/claude-scholar
Maintain a repeatable daily coding practice with Claude Scholar: pick tasks, time-box sessions, log progress, and build consistent shipping habits across small features or exercises.
About
daily-coding in claude-scholar structures repeatable daily practice for developers: session planning, focused tasks, progress notes, and habit loops that sustain momentum during active implementation.
- Daily practice routine
- Task prioritization
- Progress logging
- Consistent shipping habits
- Learner-friendly structure
Daily Coding by the numbers
- 248 all-time installs (skills.sh)
- Ranked #167 of 782 Skill Development skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/galaxy-dawn/claude-scholar --skill daily-codingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 248 |
|---|---|
| repo stars | ★ 5k |
| Last updated | July 17, 2026 |
| Repository | galaxy-dawn/claude-scholar ↗ |
What it does
Maintain a repeatable daily coding practice with Claude Scholar: pick tasks, time-box sessions, log progress, and build consistent shipping habits across small features or exercises.
Files
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, orverification-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
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}")
raiseSecurity Check Points
- User input must be validated/escaped
- Use pathlib for file paths, avoid path traversal
- Never hardcode sensitive info (API keys, passwords)