Results for “session-critique”

Runs an adversarial, decision-aware review of all session work before committing, checking decision adherence and code maintainability, and applies only user-authorized fixes.

session-stats

Generates a structured post-task reflection capturing surprises, patterns, prompt improvements, and gotchas, writing it to a markdown file without modifying project rules.

Analyzing session replays, extracting persona-based behavioral patterns, and storytelling UX issues. Reads the 'why' from real user operation logs. Works with Field/Echo for persona validation.

Runs a relentless interview that sharpens a plan or design. Use when the user wants to be grilled on an idea, pressure-test a plan, or refine a design through questioning.

Search and analyze your own session logs (older/parent conversations) using jq.

Maintains a persistent session memory across Claude sessions by loading project state at startup, capturing errors and decisions during work, and writing structured handoff summaries at session end.

Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".

Conduct a retrospective on a coding session.

Runs an interactive QA session, clarifying user-reported problems, exploring the codebase for context, and filing durable, user-focused GitHub issues.

Search and analyze your own session logs (older/parent conversations) using jq.

Search and analyze your own session logs (older/parent conversations) using jq.

Runs a structured interview session to sharpen a plan or design through relentless questioning.

Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".

Search and analyze your own session logs (older/parent conversations) using jq.

Manage and compress conversation context in long sessions. Detect when context is growing large, summarize completed work phases, archive old findings while preserving key decisions. Prevents context degradation.

Start-of-session routine — load context, check state, suggest next task. Use at the beginning of a fresh session or after a context reset.

Generates a concise status briefing after session-start reconciliation — synthesizing current state, open decisions, key risks, and today's priority actions. Use at session start, for "pk-resume", a briefing, catch-up, or today's focus.

Maintain durable session memory across agent disconnects by writing structured checkpoints to the repo's session directory, enabling context recovery.

Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".

Keeps long AI sessions on track by tracking decisions, detecting scope creep, and flagging drift before it costs work.

Runs a relentless interview session to sharpen a plan or design.

Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior sessions, previous attempts, or past investigations — even without saying 'sessions' explicitly.

Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.

session-development

Creates a technical journey retrospective document from a coding session, capturing decisions, tradeoffs, and debugging moments in a developer blog post style.

Search and analyze conversation history stored in session JSONL files using jq and shell commands.

Close a work session without losing what just happened. Write a handoff brief that captures progress, the decisions you made, the unfinished items and their next steps, and the details that would evaporate overnight, then it asks whether to commit or save it, never automatically. Trigger on "wrap up this session", "write a handoff", "close out for the day", "hand this off", "what did we get done", or the end of any working session you might have to resume later.

Search and retrieve past work from claude-mem's persistent cross-session memory database using a three-layer workflow: search, timeline, and fetch.

Search claude-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.

Use when a Claude Code session loops, drifts from scope, claims a fix that CI rejects, hits context, PATH, or permission walls, or fails in a way another retry will not solve and a root cause diagnosis is needed instead.

Use the status-briefing skill to run `pk-reconcile session-start`, then

Run multi-agent research discourse session. Use when the user requests to "start a research party" or "run a journal club".

Track open comment periods and draft a substantive, on-the-record comment that argues your position within the docket's rules and deadline.

Capture structured feedback on the Han skills and agents used in the current session and optionally post it as a GitHub issue to testdouble/han. Use at the end of any session where one or more han-* skills or agents ran, to rate a run, log what worked and what didn't, or submit observations for maintainers. Does not review code, investigate bugs, or research options; use code-review, investigate, or research for those. Does not provide feedback on skills or agents from non-Han plugins.