---
name: Feedback, bug, or feature request
about: Share feedback on a Han skill or agent, report a bug, or request a feature
title: ""
labels: []
assignees: []
---

<!--
Thanks for taking the time to send feedback. A few notes before you post,
adapted from the "How to provide feedback on Han" guide:
https://github.com/testdouble/han/blob/main/docs/how-to/provide-feedback.md

Be specific. "Han is great" and "Han is bad" are hard to act on. A concrete
moment is what helps a maintainer: "the planning skill asked me about the
database schema when the schema was right there in the code."

There are two easy ways to shape feedback before you post, and both end up
here as an issue:

1. An idea, a request, or a rough "this felt off" observation.
   Run /issue-triage in Claude Code with your note in your own words. It
   classifies the input and lists what is missing before anyone can act on
   it, so you can close those gaps now rather than waiting to be asked. Paste
   the resulting triage document below as the issue body.

2. Feedback on a session you ran.
   Install the opt-in han.feedback plugin (/plugin install han.feedback@han)
   and run /han-feedback at the end of the session, before you compact the
   context. It captures the Han skills and agents you used across the whole
   han.* family (han.core, han.github, han.reporting, han.feedback), summarizes
   what worked, what did not, and a rating, then offers to post the issue for
   you.

Prefer to write it by hand? That works too. Fill in the sections below and
delete any that do not apply, along with these instructions.
-->

## What kind of feedback is this?

<!-- Pick one: Bug · Feature request · Feedback on a skill · Question · Other -->

## Which Han skill or agent does this involve?

<!-- For example /code-review, /plan-a-feature, or an agent like risk-analyst or evidence-based-investigator. Write "not component-specific" if it is general. -->

## What happened, and what did you expect?

<!--
The concrete moment. What you saw, and what you expected instead. If this is
a feature idea, describe the job you are trying to get done and what success
would look like.
-->

## Anything that would help us reproduce or act on it?

<!--
For a bug: steps to reproduce, your environment (OS, Claude Code version), and
who or what is affected. For an idea: constraints, prior art, or the direction
you are leaning. Leave this out if nothing applies.
-->

<!--
More detail on both paths, including how to post when you do not have the gh
CLI installed:
https://github.com/testdouble/han/blob/main/docs/how-to/provide-feedback.md
-->
