kestrel

List and manage workspace TODOs for the current workspace via Kestrel DBus.

Update all documentation files to reflect recent code changes.

Use this agent when you need to manually test Kestrel extension behavior through DBus eval commands. This agent executes concrete test cases against the running GNOME Shell extension by sending commands via DBus, observing results, and reporting pass/fail status.\n\nExamples:\n\n<example>\nContext: The user has just implemented a new navigation feature and wants to verify it works in the live environment.\nuser: "I just added focusRight support. Can you test that focusing right from the leftmost window moves focus to the next window?"\nassistant: "Let me use the Task tool to launch the dbus-manual-tester agent to run this test case against the live extension."\n<commentary>\nSince the user wants to verify live behavior of the extension, use the dbus-manual-tester agent to execute the test via DBus and report results.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to verify that window creation properly updates the domain state.\nuser: "Test that after opening a new window, the world model has the correct number of windows."\nassistant: "I'll use the Task tool to launch the dbus-manual-tester agent to check the world model state via DBus after window creation."\n<commentary>\nSince the user wants to verify domain state through the running extension, use the dbus-manual-tester agent to inspect state via DBus eval.\n</commentary>\n</example>\n\n<example>\nContext: A bug was reported and the user wants to reproduce it.\nuser: "Can you check if workspace switching via Super+Down actually changes the active workspace in the domain?"\nassistant: "Let me use the Task tool to launch the dbus-manual-tester agent to test workspace switching behavior through DBus."\n<commentary>\nSince the user wants to verify a specific behavior in the running extension, use the dbus-manual-tester agent to execute commands and inspect state.\n</commentary>\n</example>

Use this agent when the user asks questions about PaperWM's behavior, architecture, implementation details, configuration options, or source code. This includes questions about how PaperWM handles window tiling, scrolling, workspaces, keybindings, animations, GNOME Shell integration, or any other PaperWM feature. Also use this agent when comparing Kestrel behavior to PaperWM's approach, or when trying to understand how PaperWM solved a particular problem.\n\nExamples:\n\n- user: "How does PaperWM handle window focus when scrolling?"\n assistant: "Let me use the paperwm-expert agent to look into PaperWM's focus handling during scrolling."\n <launches paperwm-expert agent>\n\n- user: "What signals does PaperWM listen to for window creation?"\n assistant: "I'll use the paperwm-expert agent to find the exact signals PaperWM uses for detecting new windows."\n <launches paperwm-expert agent>\n\n- user: "How does PaperWM implement its overview mode?"\n assistant: "Let me launch the paperwm-expert agent to trace through PaperWM's overview implementation."\n <launches paperwm-expert agent>\n\n- user: "We need to implement workspace switching — how does PaperWM do it?"\n assistant: "I'll consult the paperwm-expert agent to understand PaperWM's workspace switching approach so we can inform our design."\n <launches paperwm-expert agent>

13 hooks across 7 events