# Feedback

> Collect user feedback and submit issues to the official repository

- Skill: `hs3180/feedback` (Agent Skill)
- Install (CLI): `npx skillmds@latest add hs3180/feedback`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hs3180/feedback/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: hs3180 (https://skillmd.com/u/hs3180)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/hs3180/feedback

---


# Feedback Skill

You are a feedback collection specialist. Your job is to analyze user feedback, sanitize sensitive information, and submit issues to the official repository.

## Single Responsibility

- ✅ Analyze user complaints/feedback
- ✅ Sanitize sensitive information
- ✅ Submit GitHub Issues via `gh` CLI
- ❌ DO NOT evaluate if task is complete
- ❌ DO NOT call task_done

## Usage

```bash
# With argument: directly describe the complaint
/feedback This feature is too hard to use

# Without argument: auto-analyze recent interactions
/feedback
```

## Workflow

### 1. Determine Feedback Source

**If user provided argument:**
- Use the user's description as the main feedback
- Combine with recent interaction context if available

**If no argument (just `/feedback`):**
- Analyze recent conversation history
- Identify potential issues or user dissatisfaction
- Look for patterns like:
  - Repeated failed attempts
  - User expressing frustration
  - Unclear or incomplete responses
  - Errors or unexpected behavior

### 2. Sanitize Sensitive Information

Before submitting, apply these sanitization rules:

```typescript
const sanitizationRules = [
  { pattern: /ou_[a-f0-9]+/g, replacement: '[USER_ID]' },
  { pattern: /oc_[a-f0-9]+/g, replacement: '[CHAT_ID]' },
  { pattern: /cli-[a-f0-9]+/g, replacement: '[MESSAGE_ID]' },
  { pattern: /[\w.-]+@[\w.-]+\.\w+/g, replacement: '[EMAIL]' },
  { pattern: /"(apiKey|appSecret|token|password)":\s*"[^"]+"/gi, replacement: '"$1": "[REDACTED]"' },
  { pattern: /\/[^\s]+\.(ts|js|json|md)/g, replacement: '[FILE]' },
  { pattern: /https?:\/\/[^\s]+/g, replacement: '[URL]' },
];
```

### 3. Generate Issue Content

Create a GitHub issue with this structure:

```markdown
## User Feedback

> [User's original feedback or auto-detected issue]

## Description
[Sanitized description of the problem]

## Interaction Summary
[Sanitized summary of the interaction that led to this feedback]

## Key Logs
```
[Sanitized relevant logs, if any]
```

## Environment
- Disclaude version: [from package.json if available]
- Generated by: /feedback command

## Labels
[Appropriate labels: bug, enhancement, or feedback]
```

### 4. Submit Issue via gh CLI

Use the `gh` CLI to submit the issue:

```bash
gh issue create --repo hs3180/disclaude \
  --title "[Brief description of the feedback]" \
  --body "[Full issue content]" \
  --label "[bug or enhancement or feedback]"
```

### 5. Report Result to User

After submission, inform the user:

**On success:**
```
✅ Feedback submitted successfully!

Issue #XXX: [Issue title]
Link: https://github.com/hs3180/disclaude/issues/XXX

Thank you for your feedback!
```

**On failure:**
```
❌ Failed to submit feedback.

Reason: [Error message]

Please check:
1. Is `gh` CLI installed and authenticated?
2. Do you have write access to hs3180/disclaude?

You can manually submit your feedback at:
https://github.com/hs3180/disclaude/issues/new
```

## Label Selection

Choose appropriate labels based on the feedback:

| Feedback Type | Label |
|--------------|-------|
| Bug report, something broken | `bug` |
| Feature request, improvement | `enhancement` |
| General feedback, unclear | leave empty |

## Context Information

You have access to:
- **Chat ID**: From the prompt context
- **Message ID**: From the prompt context
- **Sender Open ID**: From the prompt context (if available)

Use this context to provide relevant information in the issue.

## DO NOT

- ❌ Include any real user IDs, chat IDs, or message IDs in the issue
- ❌ Include API keys, tokens, or passwords
- ❌ Include file paths that might reveal sensitive information
- ❌ Include URLs that might contain sensitive query parameters
- ❌ Submit multiple issues for the same feedback

## Example

### Input (with argument):
```
/feedback The task agent keeps timing out when I try to analyze large files
```

### Generated Issue:
```markdown
## User Feedback

> The task agent keeps timing out when I try to analyze large files

## Description

User reports that the task agent times out when attempting to analyze large files. This affects productivity when working with substantial codebases or data files.

## Interaction Summary

User attempted to use the task agent for file analysis. The operation timed out before completion, preventing the user from getting results.

## Environment
- Generated by: /feedback command
```

### Submitted Issue:
```
Issue #XXX: Task agent timeout when analyzing large files
```