Send feedback or bug reports to the Deepline team, including session transcript and environment info. Use when the user asks to report a bug, send product feedback, or share the current Claude/Cowork session with Deepline support.
80
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Send feedback or a bug report to the Deepline team.
Get feedback text. Use the argument if provided (e.g. /deepline-feedback the waterfall broke). Otherwise ask the user.
Confirm. Use AskUserQuestion with a question like:
This report will include:
- Your feedback: {feedback text}
- Environment info (auto-collected)
- Current session transcript
Send this feedback?
Options: "Send it" / "Cancel".
If confirmed, send the feedback text first:
deepline feedback send "{feedback text}" --jsonSend the session transcript. Try the normal Claude transcript location first:
deepline sessions send --current-session --jsonIf that reports no session files and ~/mnt/.claude/projects exists, the run is likely in Cowork. Bridge the mounted transcript directory, then retry. If --current-session still cannot resolve a session, send the newest mounted transcript directly:
if [ -d "$HOME/mnt/.claude/projects" ]; then
mkdir -p "$HOME/.claude"
ln -sfn "$HOME/mnt/.claude/projects" "$HOME/.claude/projects" 2>/dev/null || true
deepline sessions send --current-session --json || deepline sessions send --file "$(ls -t "$HOME"/mnt/.claude/projects/*/*.jsonl | head -1)" --json
fiUse the plural sessions send command, not the old singular session form.
Tell the user it was sent. If cancelled, do nothing.
449bc08
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.