lc-feedback

File actionable bug reports from the current Lightcone session.

18|2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/LightconeResearch/lightcone-cli --skill lc-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lc-feedback
Source: https://github.com/LightconeResearch/lightcone-cli/tree/main/claude/lightcone/skills/lc-feedback
Command: npx skills add https://github.com/LightconeResearch/lightcone-cli --skill lc-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

lc-feedback helps you quickly create a high-signal bug report tied to your current Lightcone CLI session, so maintainers can triage faster.

Core Features & Use Cases

  • Guided bug description: prompts you briefly for what went wrong if you don’t include it inline.
  • Automatic context capture: collects relevant version and environment details to include in the issue.
  • One-confirmation workflow: prepares a ready-to-file issue for the correct repo (lightcone-cli by default, with ASTRA/lc disambiguation).

Quick Start

Run: /lc-feedback <what went wrong>.

Frequently Asked Questions about lc-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I report a bug from my lightcone-cli session to GitHub?

Report a lightcone-cli session bug by running the feedback command, which automatically captures your environment context, software versions, and trimmed error output to file an actionable GitHub issue.

Do I need GitHub CLI authentication to file an issue for ASTRA spec execution errors?

Yes, GitHub CLI authentication is required to file an issue for ASTRA spec execution errors. The process checks your gh authentication status before attempting to create the bug report in the repository.

What's the best way to include repro steps when reporting lightcone container workflow failures?

Include repro steps for lightcone container workflow failures by providing a brief description of what went wrong inline when running the command; the tool handles collecting version details and OS context automatically.

How does the bug reporting tool handle sensitive data in error output?

The bug reporting tool handles sensitive data by trimming error output before submission, ensuring that only the necessary diagnostic information is included in the GitHub issue for triage.

Can I use this to create GitHub issues for scaffolding errors in a specific Lightcone repository?

Yes, you can create GitHub issues for scaffolding errors. The tool disambiguates between lightcone-cli, ASTRA, and lc repositories, filing the issue in the correct repository with a dedicated feedback label when available.

Why does my session diagnostics report fail to generate without OS context?

Session diagnostics report generation requires OS context and software versions to provide maintainers with high-signal data for triage. The tool automatically collects these environment details to ensure the issue is actionable.