beer
Skill2 starsChanged 19 days agoApache-2.0View on GitHub
End-of-day wrap-up that gathers today's wins, merged PRs, weekly stats, uncommitted work, open PRs, tomorrow's calendar, cleanup reminders, follow-ups, and standup notes. Use when the user says "end of day", "wrap up", "EOD", or runs /beer.
In this repository124 other files it gives its agents.
- add-projectSkill
- ansible-configure-vmSkill
- api-smoke-testSkill
- appinterface-checkSkill
- attach-session-to-jiraSkill
- aws-rds-debugSkill
- bootstrap-all-knowledgeSkill
- bootstrap-knowledgeSkill
- build-persona-styleSkill
- cancel-pipelineSkill
- cert-checkSkill
- check-ci-healthSkill
- check-integration-testsSkill
- check-mr-feedbackSkill
- check-my-prsSkill
- check-secretsSkill
- ci-retrySkill
- cleanup-branchesSkill
- cleanup-stale-executionsSkill
- clone-jira-issueSkill
- close-issueSkill
- close-mrSkill
- cloud-inventorySkill
- coffeeSkill
- compare-optionsSkill
- create-jira-issueSkill
- create-mrSkill
- create-slide-deckSkill
- data-migration-verifySkill
- debug-local-dbSkill
- debug-prodSkill
- deploy-to-ephemeralSkill
- dev-workflow-orchestratorSkill
- discovered-work-summarySkill
- edit-slide-deckSkill
- email-digestSkill
- environment-overviewSkill
- explain-codeSkill
- export-presentationSkill
- extend-ephemeralSkill
- find-similar-codeSkill
- gather-contextSkill
- gdrive-researchSkill
- gke-cluster-opsSkill
- hello-worldSkill
- hotfixSkill
- inscope-researchSkill
- investigate-alertSkill
- investigate-service-issuesSkill
- investigate-slack-alertSkill
- jira-hygiene-allSkill
- jira-hygieneSkill
- knowledge-refreshSkill
- konflux-statusSkill
- learn-architectureSkill
- learn-patternSkill
- list-presentationsSkill
- local-build-testSkill
- local-dev-environmentSkill
- manage-local-servicesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Use local time (Europe/Dublin):
- Very specific: line 113
Read from memory_read("state/current_work") → follow_ups list.
- Very specific: line 149
If stale_branches found and cleanup_prompts:
- Very specific: line 182
If check_known_issues returns fixes, apply them before retrying.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
beer – End of Day Wrap-Up
Overview
Gather and present an end-of-day summary. Load developer persona first; switch to devops for bonfire/ephemeral checks.
Inputs
| Input | Type | Default | Description |
generate_standup | bool | true | Generate standup notes for tomorrow |
cleanup_prompts | bool | true | Show cleanup reminders (branches, ephemeral) |
slack_format | bool | false | Use Slack link format in output |
Workflow
1. Setup
persona_load("developer")
knowledge_query(project="automation-analytics-backend", persona="developer", section="gotchas")
check_known_issues(tool_name="gitlab_mr_list")
check_known_issues(tool_name="google_calendar_list_events")2. Time-Based Greeting
Use local time (Europe/Dublin):
- < 17:00 → "Wrapping up early" ☀️
- 17:00–20:00 → "Cheers" 🍺
- > 20:00 → "Burning the midnight oil" 🌙
3. Today's Wins
git_log(repo="automation-analytics-backend", author="@me", since="today", limit=20)Parse commits for Today's Wins section.
4. Merged Today
gitlab_mr_list(project="automation-analytics/automation-analytics-backend", state="merged")Filter for today's merges (weekends: show "No MRs merged" message).
5. Weekly Stats
git_log(repo="automation-analytics-backend", author="@me", since="1 week ago", limit=100, oneline=true)
git_log(repo="automation-analytics-backend", author="@me", since="1 week ago", limit=100, numstat=true)Parse numstat for lines added/removed; count commits.
6. Uncommitted Work
Check both repos:
git_status(repo="automation-analytics-backend")
git_status(repo="redhat-ai-workflow")Include modified files in the Uncommitted Work section.
7. Open PRs
gitlab_mr_list(project="automation-analytics/automation-analytics-backend", author="@me")Indicate draft vs active.
8. Tomorrow's Calendar
google_calendar_list_events(days=2)Parse for tomorrow's events. Mark early meetings (before 10:00).
9. Ephemeral & Stale Branches
Switch to devops:
persona_load("devops")
bonfire_namespace_list(mine=true)Parse namespaces; note expiring ones.
Switch back for branches:
persona_load("developer")
git_branch_list(repo="automation-analytics-backend", merged="main")Stale branches = merged into main but not deleted (exclude main/master).
10. Follow-ups
Read from memory_read("state/current_work") → follow_ups list.
11. Standup Notes (if generate_standup)
Template:
**Yesterday:**
- [commits from today, or "(no commits today)"]
**Today:**
- [first non-draft PR, or "(check Jira board)"]
**Blockers:**
- None12. Memory Updates
memory_session_log("End of day wrap-up (beer)", "Commits: N, PRs: M")Update state/current_work:
last_beer: nowdaily_summaries: append today's stats (commits, open_prs, merged_today, uncommitted_repos)- Keep last 30 days
If standup generated:
memory_update("state/shared_context", "prepared_standup", {date, notes, generated_at})13. Chain to Cleanup
If stale_branches found and cleanup_prompts:
skill_run("cleanup_branches", '{"dry_run": true}')14. Sign-Off
- Friday: "🍻 Happy Friday! Have a great weekend!"
- Thursday: "🍺 Almost there! One more day to Friday."
- Else: "🍺 Have a good evening!"
Output Sections (in order)
- Today's Wins – commits pushed
- Merged Today – PRs merged today
- This Week's Stats – commits, lines added/removed
- Uncommitted Work – only if uncommitted changes
- Your Open PRs – active + draft
- Tomorrow's Schedule – early meetings first, then rest
- Cleanup Reminders – only if
cleanup_promptsand (expiring ephemeral or stale branches) - Follow-ups – from memory
- Tomorrow's Standup – if generated
- Sign-off
Error Handling
| Error | Pattern | Action |
| GitLab | "no such host" | learn_tool_fix("gitlab_mr_list", "no such host", "VPN not connected", "Run vpn_connect()") |
| Calendar | "oauth" / "token" | learn_tool_fix("google_calendar_list_events", "oauth token", "Token expired", "Run setup-gmail to refresh") |
| Bonfire | "no route to host" | learn_tool_fix("bonfire_namespace_list", "no route to host", "VPN not connected", "Run vpn_connect() and kube_login('ephemeral')") |
If check_known_issues returns fixes, apply them before retrying.
MCP Tools
| Tool | Purpose |
persona_load | developer → devops (ephemeral) → developer |
knowledge_query | Project gotchas |
check_known_issues | gitlab_mr_list, google_calendar_list_events |
git_log | Today's commits, weekly stats (oneline, numstat) |
git_status | automation-analytics-backend, redhat-ai-workflow |
git_branch_list | Branches merged into main |
gitlab_mr_list | Merged PRs, my open PRs |
bonfire_namespace_list | Ephemeral namespaces (mine) |
google_calendar_list_events | Tomorrow's schedule (days=2) |
memory_session_log | Log EOD |
memory_read / memory_update | current_work, shared_context |
learn_tool_fix | On VPN/calendar/bonfire failures |
skill_run | cleanup_branches (dry_run) |
Repos
- automation-analytics-backend – main work
- redhat-ai-workflow – workflow tooling
GitLab
- Project:
automation-analytics/automation-analytics-backend - MR base:
https://gitlab.cee.redhat.com/automation-analytics/automation-analytics-backend/-/merge_requests
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

