start-of-day
Start of Day - Universal Project Sync
This skill performs a comprehensive analysis of the current working directory to get you synced up at the start of each day. It works on any project.
What This Skill Does
-
Git Repository Check
- Detects if current directory is a git repo
- Fetches and pulls latest changes if behind
- Reports current branch and status
- Shows recent commits
-
Codebase Analysis
- Reads all key files in the project
- Identifies tech stack and architecture
- Reviews project structure
- Identifies what's built vs pending
-
Documentation Review
- Reads all markdown files
- Reviews any documentation folders
- Identifies action items and TODOs
-
Status Report
- Git sync summary
- Project overview
- Key files and structure
- Recommended next steps
Execution Steps
Step 1: Git Repository Check
Check if the current working directory (or any subdirectories) contains git repos:
# Check if current directory is a git repo
git status 2>/dev/null
# If it's a repo, fetch and check status
git fetch origin 2>/dev/null
git status -sb
# Check if behind remote
git rev-list HEAD..@{u} --count 2>/dev/null
# Pull if behind
git pull
# Show recent commits
git log --oneline -10
If the current directory is not a git repo, check subdirectories for git repos and report on each.
Step 2: Read Project Files
Read key files to understand the project:
-
Configuration files (use Glob to find, then Read):
package.json,requirements.txt,Cargo.toml, etc..env.example, config filesREADME.md,CONTRIBUTING.md
-
Source code structure (use Glob):
- Find main entry points
- Identify src/lib/app directories
- Map out the project structure
-
Documentation (use Glob + Read):
- All
*.mdfiles - Any
docs/folder contents - Implementation plans, specs
- All
Step 3: Codebase Exploration
Use the Explore agent to thoroughly analyze the codebase:
- Technology stack (frameworks, languages)
- Project architecture
- Key components and their purposes
- Dependencies and their versions
- What's implemented vs TODO comments
Step 4: Generate Report
Provide a structured report:
A. Git Status
- Current branch
- Sync status (up to date / pulled X commits)
- Recent commits
- Any uncommitted changes
B. Project Overview
- Tech stack
- Project structure
- Key files and entry points
- Dependencies
C. Documentation Summary
- Key docs found
- Important notes
- TODOs and action items
D. Recommended Next Steps
- What to focus on
- Pending work identified
- Any issues to address
Tool Usage
This skill uses:
Bash- For git operationsGlob- To find files by patternRead- To read file contentsTaskwithExploreagent - For deep code analysisTodoWrite- To track analysis progress
Important Notes
- Works on current directory - No hardcoded paths
- Adapts to any project - Detects project type automatically
- Pulls git updates - Keeps you in sync with remote
- Reads all relevant files - Builds full context
Activation Triggers
This skill activates when user says:
- "start of day"
- "daily sync"
- "start the day"
- "project status"
- "sync me up"
- "get me up to speed"
More from claude-code-community-ireland/claude-code-resources
design-ui
This skill should be used when the user asks to "design a UI", "create a landing page", "build a dashboard", "generate a website design", "make a product page", or needs guidance on UI design patterns, accessibility standards, design tokens, or eliminating generic AI-generated design patterns (vibe-code).
12security-review
Security review checklist covering OWASP Top 10, authentication, authorization, input validation, secrets management, and common vulnerability patterns. Reference when reviewing code for security.
7design-patterns
Reference library of proven UI design patterns, component templates, and sector-specific conventions for high-quality design generation.
6architecture-decision-record
ADR format and methodology for documenting significant technical decisions with context, alternatives considered, and consequences. Use when making or documenting architectural decisions.
5pr-description
Pull request authoring standards — structured descriptions, linking issues, providing test evidence, and writing good summaries. Reference when creating or describing pull requests.
4refactoring-patterns
Safe refactoring techniques — extract method, rename, move, inline, and structural patterns. Includes code smell identification and transformation recipes. Use when refactoring code or improving structure.
4