command-after-fail

Analyze shell and git command failure outputs to identify error types and recommend solutions.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/dong-frank/FeishuAI --skill command-after-fail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-after-fail
Source: https://github.com/dong-frank/FeishuAI/tree/main/skills/command-after-fail
Command: npx skills add https://github.com/dong-frank/FeishuAI --skill command-after-fail

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users troubleshoot command-line failures by analyzing error outputs and providing targeted, easy-to-understand solutions, reducing downtime and confusion.

Core Features & Use Cases

  • Error Analysis: Interprets command failures from stderr, stdout, and exit codes to identify common issues like syntax errors or permission problems.
  • Context-Aware Troubleshooting: Uses repository and command context to determine whether issues are configuration, permission, or project-specific.
  • Use Case: When a developer encounters a failed git push, this Skill assesses the error and suggests the appropriate fix or relevant documentation, saving time on manual investigation.

Quick Start

Provide the failed command output to the AI and ask for a diagnosis and suggested fix.

Frequently Asked Questions about command-after-fail

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

FAQPage Schema
How do I troubleshoot a git command error after a failed push or commit?

Git command errors can be diagnosed by providing the failed command output to the AI for analysis. It parses stderr, stdout, and exit codes to identify whether the issue stems from syntax errors, permission problems, or configuration, then recommends the appropriate fix.

Can I use this to diagnose build and deployment command failures?

Build and deployment command failures are supported by this Skill. It analyzes error outputs from shell or version control systems to determine whether issues are configuration, permission, or project-specific, providing targeted fixes to reduce downtime.

What is the best way to analyze shell command errors and stderr outputs?

The best way to analyze shell command errors is to provide the failed command output to the AI for diagnosis. It interprets stderr, stdout, and exit codes to identify error types and suggests the appropriate fix or relevant documentation, reducing manual investigation.

Does diagnosing command errors require repository context or project data?

Diagnosing command errors leverages repository context if available to determine whether issues are configuration, permission, or project-specific. Providing contextual repository data helps apply context-aware troubleshooting for more accurate solutions.

Why does my version control command fail and how do I resolve the issue?

Version control command failures can stem from syntax errors, permission problems, or configuration issues. Provide the failed command output to the AI for diagnosis to identify the specific error type and receive recommended troubleshooting steps to resolve the issue.