pocket-sized atproto pitch waow.tech
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

remove .claude commands

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

zzstoatzz ef595504 b89a6045

-66
-66
.claude/commands/digest.md
··· 1 - --- 2 - description: generate a digest of work shipped over the last month 3 - allowed-tools: Bash(git:*), Bash(ls:*), Bash(gh:*), Bash(find:*), Bash(stat:*), Read, Glob, Grep, Task 4 - --- 5 - 6 - generate a comprehensive digest of what i've shipped over the last month. 7 - 8 - ## step 1: detect identity 9 - 10 - determine who the user is by running these commands: 11 - - `git config user.email` - primary identifier for commit authorship 12 - - `git config user.name` - display name 13 - - `gh api user --jq .login 2>/dev/null` - github username (skip if gh unavailable) 14 - 15 - ## step 2: detect source directories 16 - 17 - check for these directory structures and skip any that don't exist: 18 - 19 - **github repos**: `~/github.com/{username}` where username matches the gh login or can be inferred from directory contents 20 - 21 - **tangled repos**: `~/tangled.sh/@{handle}` - look for directories matching `@*` pattern 22 - 23 - **gitlab repos**: `~/gitlab.com/{username}` (if exists) 24 - 25 - for each provider, only proceed if the base directory exists (e.g., `~/github.com`). 26 - 27 - ## step 3: find recently modified repos 28 - 29 - for each detected source directory: 30 - 1. list subdirectories and check modification times 31 - 2. for repos modified in the last 30 days, run: `git log --oneline --author="<email>" --since="1 month ago" | head -20` 32 - 3. skip repos with no commits from this user in the time period 33 - 34 - also check for work contributions in common locations: 35 - - employer repos (other directories under ~/github.com that aren't the user's username) 36 - - look for repos where the user has commits but doesn't own the repo 37 - 38 - ## step 4: gather project metadata 39 - 40 - for each active repo, try to determine: 41 - - **what it is**: read README.md first paragraph or pyproject.toml description 42 - - **live url**: check for fly.toml (app name -> {app}.fly.dev), wrangler.toml, vercel.json, or CNAME files 43 - - **package name**: check pyproject.toml `[project] name` for installable packages 44 - 45 - ## step 5: generate digest 46 - 47 - organize the output as markdown: 48 - 49 - ``` 50 - ## shipped this month 51 - 52 - ### projects 53 - | project | description | link | 54 - |---------|-------------|------| 55 - | ... | ... | ... | 56 - 57 - ### contributions 58 - notable commits to other projects (employer, open source, etc.) 59 - 60 - ### themes 61 - - common patterns or focus areas this month 62 - ``` 63 - 64 - include valid links wherever possible - deployed URLs, github repos, pypi packages. 65 - 66 - format should be suitable for embedding in a personal site or sharing as a status update.