@Tak Lo love this! Great idea

Hey, just curious if anybody here is using Notion AI. I was just watching a podcast called "Behind the Craft" It took Akshay (Notion’s co-founder) and Ryan (AI lead) 2 years of failure to build agents that can create databases, respond to Slack, and more. We had a great chat about their most surprising lessons from building the best AI agents for work. I use Notion every day, but I have not yet tried Notion AI, but I'm definitely going to consider it. I use Notion everyday, I haven't tried Notion AI yet but Definitely considering giving it a try. https://youtu.be/yflqBe9Bj4E

Use this prompt when critical issues arise that cannot be quickly fixed forward and you need to restore the codebase to a known stable state. Instead of manually executing complex git commands that could permanently delete work if done incorrectly, this prompt guides an LLM agent through a safe, documented rollback procedure with built-in safety checks. The LLM will automatically create a backup of the current state before rolling back, stop for your approval before force-pushing, and provide verification at each step—preventing the costly mistakes that often occur during high-pressure emergency situations when you're trying to restore production systems. Here's the prompt: # LLM Prompt: Rollback to Last Stable Checkpoint ``` I need you to perform a rollback of the {{{YOUR APPLICATION NAME}}} develop branch to the last stable checkpoint. This is an emergency rollback procedure due to critical issues that cannot be quickly fixed forward. ## Current Situation - The develop branch has critical issues that are blocking progress - We need to rollback to the last known stable state - We have a documented stable checkpoint that we need to restore ## Checkpoint Information Please reference the file `docs/ROLLBACK_PROCEDURES.md` to find the "Current Stable Backup Points" section which contains: - Tag name (format: v[VERSION]-stable) - Branch name (format: backup/pre-[feature]-YYYY-MM-DD) - Commit hash - Project status at that point ## Your Task Follow these steps carefully: 1. **Read the Documentation First** - Read `docs/ROLLBACK_PROCEDURES.md` completely - Identify the latest stable checkpoint from the "Current Stable Backup Points" section - Note the backup branch name and tag name 2. **Create a Safety Backup of Current State** Before doing ANY rollback, create a backup of the current develop state: ```bash git checkout develop git branch develop-pre-rollback-$(date +%Y%m%d-%H%M%S) git push origin develop-pre-rollback-$(date +%Y%m%d-%H%M%S)

Use this prompt when you've reached a stable milestone and want to create a rollback point before starting new development work. Rather than manually remembering the specific naming conventions, git commands, and documentation updates required for a proper checkpoint, this prompt automates the entire process through an LLM agent. The agent will gather your project's current status, create properly named tags and branches following your established conventions, update all relevant documentation files, and verify everything was created successfully—ensuring consistency across checkpoints and eliminating the human error that occurs when manually creating backups during busy development periods. Here's the prompt: # LLM Prompt: Create New Stable Checkpoint ``` I need you to create a new stable checkpoint (backup branch and tag) for {{{YOUR APPLICATION NAME}}}. We've reached a stable milestone and want to create a rollback point before continuing with new development. ## Current Situation - We've reached a significant milestone or stable point - All tests are passing and the application is stable - We want to create a checkpoint before starting new feature development - This checkpoint will serve as a rollback point if issues arise ## Your Task Follow the procedure documented in `docs/CREATING_STABLE_CHECKPOINTS.md` to create a new checkpoint. ### Step 1: Gather Information First, gather the required information: ```bash # 1. Get current version cat VERSION # 2. Get Task Master status task-master list --status=all # 3. Get current commit info git log -1 --format="%H %s" # 4. Verify we're on develop and up to date git branch --show-current git status git pull origin develop ``` Show me this information before proceeding. ### Step 2: Confirm Details With Me Before creating the checkpoint, ask me: 1. What feature or milestone are we about to START working on next? (for naming) 2. Confirm the current version number from VERSION file

Has anybody else used this? I bookmarked it. I never did go back and try it out, but it looks actually really cool. Built by ex-AI engineers from Meta, Microsoft, and Amazon. Launch & Control Claude Code from Anywhere Stop being chained to your desk. The real-time command center to monitor, debug, and guide your agent—right from your phone. https://omnara.com/