✨ Add commit count picker modal for quick ref selection

Introduce a new modal (triggered by '#' in PR mode) that lets users
quickly set a "from" reference to HEAD~N. This provides a faster
alternative to manually typing refs for common "last N commits" workflows.

The commit count picker:
- Supports PR, Review, Changelog, and Release Notes modes
- Shows a live preview of the resulting HEAD~N ref
- Validates input to ensure count > 0

Also enhance the ref selector to accept custom input when no matching
branch is found, allowing freeform refs like HEAD~5 to be entered
directly.

Author: hyperb1iss

src/agents/capabilities/pr.toml

@@ -3,7 +3,7 @@ description = "Generate pull request descriptions from commits and changes"
 output_type = "MarkdownPullRequest"
 
 task_prompt = """
-You are Iris, an expert AI assistant creating professional pull request descriptions. Treat the commits and diffs as a cohesive unit and explain their purpose, impact, and testing status.
+You are Iris, an expert AI assistant creating compelling pull request descriptions. Your PRs should be engaging, well-organized, and tell a story about what this change accomplishes.
 
 ## MANDATORY FIRST STEP
 **ALWAYS call `project_docs(doc_type="context")` FIRST** before any other tool.
@@ -34,23 +34,44 @@ Return a JSON object with a single `content` field containing your markdown PR d
 }
 ```
 
+## Critical Writing Approach
+
+**FOCUS ON CAPABILITIES, NOT FILES**
+
+❌ DON'T write like this:
+- "Modified `src/auth.rs` to add login function"
+- "Updated `user.rs` with new fields"
+- "Changed `config.toml` to include new settings"
+
+✅ DO write like this:
+- "Users can now authenticate via OAuth2 or API key"
+- "Session management persists across browser restarts"
+- "New configuration options control token expiration and refresh behavior"
+
+Think about:
+- What can users/developers DO now that they couldn't before?
+- What problems does this solve?
+- What's the user-facing or developer-facing impact?
+
 ## Structure Guidelines
 
 Organize your PR naturally. A typical structure might include:
 
-- **Title** (H1) — Clear, descriptive title with optional emoji
-- **Summary** — Brief overview of what this PR accomplishes
-- **Description** — Detailed explanation organized by sections:
-  - Core Capabilities, Technical Details, API Changes, etc.
+- **Title** (H1) — Clear, descriptive title with emoji
+- **Summary** — What this PR enables (1-2 sentences, capability-focused)
+- **What's New** — Bullet list of capabilities/features (not files!)
+- **How It Works** — Technical explanation if needed, organized by concept
 - **Commits** — List of commit messages included
 - **Breaking Changes** — Impact statements and migration guidance (if any)
 - **Testing** — How to verify the changes work
 - **Notes** — Additional context for reviewers
 
-Adapt the structure based on what makes sense for this specific PR. Let the content drive the organization.
+Adapt the structure based on what makes sense for this specific PR.
 
 ## Writing Standards
 
+- Lead with **capabilities and outcomes**, not implementation details
+- Group related changes by **what they accomplish**, not by file
 - Explain **why** changes were made, not just what changed
 - Use `backticks` for code references: files, modules, functions, commands, types
 - Use **bold** for key concepts and emphasis
@@ -63,59 +84,65 @@ Adapt the structure based on what makes sense for this specific PR. Let the cont
 ## Example Format
 
 ```markdown
-# ✨ Add comprehensive Experience Fragment management
+# ✨ Experience Fragment Lifecycle Management
 
 ## Summary
 
-Implements full lifecycle support for Experience Fragments including creation, updates, linking, and deletion. This enables content authors to manage XF components directly through the API.
+Content authors can now create, update, link, and delete Experience Fragments directly through the API — no manual AEM console navigation required.
 
-## Description
+## 🎯 What's New
 
-### Core Capabilities
+- **Full XF lifecycle** — Create fragments from templates, update content, manage links, delete with cascade
+- **Auto-linking** — Fragments automatically resolve cross-references to related content
+- **Template-based creation** — Start from pre-defined templates with sensible defaults
+- **Cascade deletion** — Remove fragments and optionally clean up all linked content
 
-- Introduced `XFManager` in `src/services/xf.rs` providing **unified XF operations**
-- New `ExperienceFragment` model with full validation and serialization support
-- Added `XFLinkResolver` for automatic cross-reference resolution
+## ⚙️ How It Works
 
-### API Changes
+### API Endpoints
 
-- `POST /api/xf` — Create new Experience Fragment
-- `PUT /api/xf/:id` — Update existing fragment
-- `DELETE /api/xf/:id` — Remove fragment (with cascade option)
+| Method | Endpoint | Purpose |
+|--------|----------|---------|
+| `POST` | `/api/xf` | Create new fragment from template |
+| `PUT` | `/api/xf/:id` | Update fragment content |
+| `DELETE` | `/api/xf/:id` | Remove fragment (cascade optional) |
 
 ### Configuration
 
-New config options in `config.toml`:
-- `xf.default_template` — Default template for new fragments
-- `xf.cascade_delete` — Whether deletions cascade to linked content
+Add to your `config.toml`:
+```toml
+[xf]
+default_template = "hero-banner"
+cascade_delete = true
+```
 
-## Commits
+## 📋 Commits
 
-- `abc1234`: feat: add XF lifecycle management
-- `def5678`: feat: implement link resolver
-- `ghi9012`: test: add XF integration tests
+- `abc1234` ✨ feat: add XF lifecycle management
+- `def5678` 🔗 feat: implement link resolver
+- `ghi9012` ✅ test: add XF integration tests
 
-## Breaking Changes
+## ⚠️ Breaking Changes
 
-- **Removed `legacyXF` endpoint** — Use `/api/xf` instead. Old endpoints will 404.
-- **Config schema update** — Add `xf` section to your config file.
+- **Legacy endpoint removed** — `/legacyXF/*` routes now return 404. Migrate to `/api/xf`.
+- **Config required** — Add `[xf]` section to config before using XF features.
 
-## Testing
+## 🧪 Testing
 
-1. Create a new XF via POST /api/xf with template body
-2. Verify XF appears in content listing
-3. Update XF and confirm changes persist
-4. Delete XF and verify cascade behavior
+1. Create a new XF: `POST /api/xf` with template body
+2. Verify it appears in the content listing
+3. Update the XF and confirm changes persist
+4. Delete and verify cascade behavior matches config
 
-## Notes
+## 📝 Notes
 
-- Tenants must configure `experienceFragmentComponentType` before using XF features
-- Performance testing recommended for sites with >1000 XFs
+- Configure `experienceFragmentComponentType` in tenant settings first
+- Performance testing recommended for sites with >1000 fragments
 ```
 
-## Emoji Placement
+## Emoji Usage
 
-- When gitmoji enabled: ONE emoji in the H1 title, emojis in section headers for visual structure
-- Keep actual content clean — no scattered emojis in prose
-- When conventional preset: NO emojis anywhere
+Follow the emoji styling instructions injected by the system:
+- **When gitmoji enabled**: Use emojis in H1 title and section headers (🎯, ⚙️, 📋, ⚠️, 🧪, 📝). Include gitmoji from commits. Keep body text clean.
+- **When conventional/no-emoji preset**: No emojis anywhere — plain text only.
 """

src/agents/iris.rs

@@ -667,13 +667,19 @@ Guidelines:
             if gitmoji_enabled {
                 system_prompt.push_str("\n\n=== EMOJI STYLING ===\n");
                 system_prompt.push_str(
-                    "Include ONE relevant gitmoji at the start of the H1 title to indicate the primary type of change. ",
+                    "Use emojis to make the output visually scannable and engaging:\n",
                 );
                 system_prompt.push_str(
-                    "You may optionally add emojis to section headers (## headings) for visual structure. ",
+                    "- H1 title: ONE gitmoji at the start (✨, 🐛, ♻️, etc.)\n",
                 );
                 system_prompt.push_str(
-                    "Keep prose content clean - no scattered emojis within sentences or bullet points. ",
+                    "- Section headers (## headings): Add relevant emojis (🎯 What's New, ⚙️ How It Works, 📋 Commits, ⚠️ Breaking Changes, 🧪 Testing, 📝 Notes)\n",
+                );
+                system_prompt.push_str(
+                    "- Commit list entries: Include the gitmoji from each commit\n",
+                );
+                system_prompt.push_str(
+                    "- Body text: Keep clean - no scattered emojis within prose\n\n",
                 );
                 system_prompt.push_str("Choose from this gitmoji list:\n\n");
                 system_prompt.push_str(&crate::gitmoji::get_gitmoji_list());

src/cli.rs

@@ -188,6 +188,14 @@ pub enum Commands {
         #[arg(long, help = "Output raw markdown without any console formatting")]
         raw: bool,
 
+        /// Copy raw markdown to clipboard
+        #[arg(
+            short,
+            long,
+            help = "Copy raw markdown to clipboard (for pasting into GitHub/GitLab)"
+        )]
+        copy: bool,
+
         /// Starting branch, commit, or commitish for comparison
         #[arg(
             long,
@@ -1127,9 +1135,10 @@ pub async fn handle_command(
             common,
             print,
             raw,
+            copy,
             from,
             to,
-        } => handle_pr(common, print, raw, from, to, repository_url).await,
+        } => handle_pr(common, print, raw, copy, from, to, repository_url).await,
         Commands::Studio {
             common,
             mode,
@@ -1234,14 +1243,16 @@ async fn handle_pr_with_agent(
     common: CommonParams,
     print: bool,
     raw: bool,
+    copy: bool,
     from: Option<String>,
     to: Option<String>,
     repository_url: Option<String>,
 ) -> anyhow::Result<()> {
+    use arboard::Clipboard;
     use crate::agents::{IrisAgentService, StructuredResponse, TaskContext};
     use crate::instruction_presets::PresetType;
 
-    // Check if the preset is appropriate for PR descriptions (skip for raw output)
+    // Check if the preset is appropriate for PR descriptions (skip for raw output only)
     if !raw
         && !common.is_valid_preset_for_type(PresetType::Review)
         && !common.is_valid_preset_for_type(PresetType::Both)
@@ -1255,7 +1266,7 @@ async fn handle_pr_with_agent(
     // Create structured context for PR (handles defaults: from=main, to=HEAD)
     let context = TaskContext::for_pr(from, to);
 
-    // Create spinner for progress indication (skip for raw output)
+    // Create spinner for progress indication (skip for raw output only)
     let spinner = if raw {
         None
     } else {
@@ -1276,7 +1287,31 @@ async fn handle_pr_with_agent(
         return Err(anyhow::anyhow!("Expected pull request response"));
     };
 
-    if raw || print {
+    // Handle clipboard copy
+    if copy {
+        let raw_content = generated_pr.raw_content();
+        match Clipboard::new() {
+            Ok(mut clipboard) => match clipboard.set_text(raw_content) {
+                Ok(()) => {
+                    ui::print_success("PR description copied to clipboard");
+                }
+                Err(e) => {
+                    ui::print_error(&format!("Failed to copy to clipboard: {e}"));
+                    // Fall back to printing raw
+                    println!("{raw_content}");
+                }
+            },
+            Err(e) => {
+                ui::print_error(&format!("Clipboard unavailable: {e}"));
+                // Fall back to printing raw
+                println!("{raw_content}");
+            }
+        }
+    } else if raw {
+        // Raw markdown for piping to files or APIs
+        println!("{}", generated_pr.raw_content());
+    } else if print {
+        // Formatted output for terminal viewing
         println!("{}", generated_pr.format());
     } else {
         ui::print_success("PR description generated successfully");
@@ -1291,26 +1326,29 @@ async fn handle_pr(
     common: CommonParams,
     print: bool,
     raw: bool,
+    copy: bool,
     from: Option<String>,
     to: Option<String>,
     repository_url: Option<String>,
 ) -> anyhow::Result<()> {
     log_debug!(
-        "Handling 'pr' command with common: {:?}, print: {}, raw: {}, from: {:?}, to: {:?}",
+        "Handling 'pr' command with common: {:?}, print: {}, raw: {}, copy: {}, from: {:?}, to: {:?}",
         common,
         print,
         raw,
+        copy,
         from,
         to
     );
 
-    // For raw output, skip all formatting
+    // For raw output, skip version banner (piped output should be clean)
+    // For copy mode, show the banner since we're giving user feedback
     if !raw {
         ui::print_version(crate_version!());
         ui::print_newline();
     }
 
-    handle_pr_with_agent(common, print, raw, from, to, repository_url).await
+    handle_pr_with_agent(common, print, raw, copy, from, to, repository_url).await
 }
 
 /// Handle the `Studio` command

src/studio/handlers/modals/commit_count.rs

@@ -0,0 +1,79 @@
+//! Commit count picker modal key handler
+//!
+//! Quick picker for "last N commits" - sets `from_ref` to HEAD~N
+
+use crossterm::event::{KeyCode, KeyEvent};
+
+use crate::studio::events::SideEffect;
+use crate::studio::state::{CommitCountTarget, Modal, Notification, StudioState};
+
+use super::super::{
+    reload_changelog_data, reload_pr_data, reload_release_notes_data, reload_review_data,
+};
+
+/// Handle key events in commit count modal
+pub fn handle(state: &mut StudioState, key: KeyEvent) -> Vec<SideEffect> {
+    // Get current state
+    let (input, target) = if let Some(Modal::CommitCount { input, target }) = &state.modal {
+        (input.clone(), *target)
+    } else {
+        return vec![];
+    };
+
+    match key.code {
+        KeyCode::Esc => {
+            state.close_modal();
+            vec![]
+        }
+        KeyCode::Enter => {
+            // Parse the number and set HEAD~N
+            let count: usize = input.parse().unwrap_or(0);
+            if count == 0 {
+                state.notify(Notification::error("Please enter a number > 0"));
+                return vec![];
+            }
+
+            let ref_value = format!("HEAD~{count}");
+            let (label, effect) = match target {
+                CommitCountTarget::Pr => {
+                    state.modes.pr.base_branch.clone_from(&ref_value);
+                    ("PR base", reload_pr_data(state))
+                }
+                CommitCountTarget::Review => {
+                    state.modes.review.from_ref.clone_from(&ref_value);
+                    ("Review from", reload_review_data(state))
+                }
+                CommitCountTarget::Changelog => {
+                    state.modes.changelog.from_ref.clone_from(&ref_value);
+                    ("Changelog from", reload_changelog_data(state))
+                }
+                CommitCountTarget::ReleaseNotes => {
+                    state.modes.release_notes.from_ref.clone_from(&ref_value);
+                    ("Release Notes from", reload_release_notes_data(state))
+                }
+            };
+
+            state.notify(Notification::info(format!(
+                "{label} set to last {count} commits"
+            )));
+            state.close_modal();
+            vec![effect]
+        }
+        // Quick presets: 1-9 for immediate selection
+        KeyCode::Char(c) if c.is_ascii_digit() => {
+            if let Some(Modal::CommitCount { input, .. }) = &mut state.modal {
+                input.push(c);
+            }
+            state.mark_dirty();
+            vec![]
+        }
+        KeyCode::Backspace => {
+            if let Some(Modal::CommitCount { input, .. }) = &mut state.modal {
+                input.pop();
+            }
+            state.mark_dirty();
+            vec![]
+        }
+        _ => vec![],
+    }
+}

src/studio/handlers/modals/mod.rs

@@ -3,6 +3,7 @@
 //! Each modal type has its own handler module for maintainability.
 
 mod chat;
+mod commit_count;
 mod confirm;
 mod emoji_selector;
 mod instructions;
@@ -34,6 +35,7 @@ pub fn handle_modal_key(state: &mut StudioState, key: KeyEvent) -> Vec<SideEffec
         Some(Modal::EmojiSelector { .. }) => emoji_selector::handle(state, key),
         Some(Modal::Settings(_)) => settings::handle(state, key),
         Some(Modal::ThemeSelector { .. }) => theme_selector::handle(state, key),
+        Some(Modal::CommitCount { .. }) => commit_count::handle(state, key),
         None => vec![],
     }
 }