# How to Report Bugs in Leonxlnx/taste-skill: Issues, PRs, and Contact Options

> Learn how to report bugs effectively in Leonxlnx/taste-skill. Discover GitHub issue and PR procedures, plus direct contact options for swift resolution.

- Repository: [Leon Lin/taste-skill](https://github.com/Leonxlnx/taste-skill)
- Tags: how-to-guide
- Published: 2026-05-26

---

**Report bugs in Leonxlnx/taste-skill by opening a GitHub issue or pull request, or contact maintainers privately via X (Twitter) at @lexnlin or @blueemi99, or email hello@tasteskill.dev.**

The Leonxlnx/taste-skill repository provides multiple channels for defect reporting to accommodate different communication preferences and privacy needs. Whether you encounter issues with the **skill.sh** deployment script or individual skill definitions in **skills/*/SKILL.md**, following the project's established process ensures your report reaches maintainers efficiently.

## Bug Reporting Channels for Leonxlnx/taste-skill

The project offers three distinct pathways to surface defects, documented in **README.md** lines 38-45.

### GitHub Issues and Pull Requests

The primary method for reporting bugs involves creating a new issue in the [Leonxlnx/taste-skill](https://github.com/Leonxlnx/taste-skill) repository. If you have implemented a fix, submit a **pull request** that references the related issue using the "Fixes #123" syntax. The project's CI pipeline runs automatically on PR submissions, triggering reviewer notifications and automated tests.

### Direct Messages on X (Twitter)

For private discussions or sensitive security issues, message the core contributors directly on X. Contact **@lexnlin** or **@blueemi99** for informal inquiries or when you prefer not to disclose details publicly.

### Email Support

Send detailed, formal reports to **hello@tasteskill.dev**. This channel is ideal for complex technical issues requiring extensive attachments, logs, or legal considerations.

## Essential Information to Include

Every bug report should contain these elements to ensure maintainers can reproduce and diagnose the issue:

- **Concise title** describing the symptom.
- **Steps to reproduce** with minimal, specific examples.
- **Expected versus actual behavior** comparison.
- **Environment details** including OS, Node version, and skill version.
- **Relevant logs or screenshots** showing error output.

## Creating a High-Quality Bug Report

When filing an issue in Leonxlnx/taste-skill, structure your report using this template format:

```markdown

## Summary

A short description of the bug.

## Steps to Reproduce

1. Run `npx skills add https://github.com/Leonxlnx/taste-skill --skill "design-taste-frontend"`.
2. Provide the prompt ___.
3. Observe the unexpected output.

## Expected Result

What should happen.

## Actual Result

What actually happens (include logs or screenshots).

## Environment

- OS: macOS 14.2
- Node: 20.10.0
- Skill version: v2.0.0

```

## Submitting a Fix via Pull Request

If you have resolved a bug in **skill.sh** or a **SKILL.md** file, contribute the fix using standard Git workflows:

```bash

# Fork the repo, create a branch, edit files, then:

git commit -am "Fix typo in SKILL.md frontmatter"
git push origin my-fix-branch

# Open a PR on GitHub linking to the issue:

#   "Fixes #42 – typo in skill name"

```

## Key Source Files to Reference

Understanding these files helps identify where bugs originate and where fixes should be applied:

- **README.md** (lines 38-44, 42-45): Contains central documentation and bug-reporting instructions.
- **skill.sh**: Helper script used by the `npx skills` CLI; common source of runtime errors.
- **skills/*/SKILL.md**: Individual skill definitions that may contain logic errors or documentation bugs.
- **CHANGELOG.md**: History of changes useful for determining if a bug is a regression.
- **LICENSE**: Legal information required for all contributions.

## Summary

- Open GitHub issues or pull requests in Leonxlnx/taste-skill for public bug tracking and collaborative fixes.
- Contact @lexnlin or @blueemi99 on X for private communication channels.
- Email hello@tasteskill.dev for formal or detailed technical reports requiring attachments.
- Include reproduction steps, environment details, and logs in every report to ensure efficient resolution.
- Reference specific files like **skill.sh** or **skills/*/SKILL.md** when describing the bug location.

## Frequently Asked Questions

### Can I report bugs privately instead of using GitHub issues?

Yes. According to the README.md documentation (lines 42-45), you can DM @lexnlin or @blueemi99 on X (formerly Twitter) or email hello@tasteskill.dev for private bug reports that you do not wish to disclose publicly.

### What information should I include when reporting a bug in Leonxlnx/taste-skill?

Include a descriptive title, precise steps to reproduce, expected versus actual behavior, environment specifications such as OS and Node version, and any relevant logs or screenshots. This information allows maintainers to reproduce the issue in **skill.sh** or the specific skill module.

### How do I submit a fix for a bug I found in the skill.sh script?

Fork the Leonxlnx/taste-skill repository, create a feature branch, commit your changes with a descriptive message referencing the issue, push to your fork, and open a pull request on GitHub. Use the "Fixes #123" syntax in your PR description to link it to the original issue.

### Where can I check if a bug has already been reported or fixed?

Review the **CHANGELOG.md** file in the repository root for historical fixes and search existing GitHub issues in Leonxlnx/taste-skill before creating a new report to avoid duplicates.