Engineering Operations · Automation Pack
Engineering leads rely on Hana to keep rituals humming by drafting standups, logging tasks, scheduling reminders, and compiling release procedures straight from chat. Use this pack instead of jumping between multiple guides.
Keep Context In Hana
Sync PR links, sprint notes, OTA guides, and reminders so Hana can reuse them across every workflow below.
Daily Standup Reports
- Invocation:
@Hana update these progress in daily_standup report group - What you get: A formatted report message (bullets + edit link) posted to the report group.
- Sample output: Notes on testing Grok 4.1, long-text summarization work, and PR status with a dashboard edit URL.
Quick Task Creation
- Invocation:
@Hana add a task for <users/102606422926865728187> to evaluate upgradation to grok 4.1 - What you get: Task title, detailed notes/checklist, reference links, and dashboard edit link.
- Sample output: Grok 4.1 evaluation task covering improvements, benchmarks, tech requirements, known issues, and deliverable expectations.
Release Procedure Documentation
- Invocation:
@Hana create a documentation for release procedure by considering the new deployment keys. - What you get: Long-form ship plan covering prerequisites, CLI commands, deployment key setup, release steps, rollbacks, and best practices.
- Sample output: Juice APK release doc with Revopush commands (
revopush deployment add,release-react,rollback), targeting binary versions, and security notes.
Reminder Scheduling
- Invocation:
@Hana remind <users/102606422926865728187> to do this today afternoon to add some suggestions for the website revamp - What you get: Confirmation with timestamp (e.g., Nov 18, 2025 @ 2 PM IST), reminder description, reminder ID, and dashboard link.
- Sample output: Reminder for Sagar Kapoor to review the Figma Hanabi redesign thread and add suggestions.
Extend The Pack
- Chain reminders and tasks (e.g., create task → set reminder).
- Store final release docs back into memories so future runs stay accurate.