Skip to content
Agentmart
Submit a tool

fullstack-ship-troubleshooter

Diagnose and fix fullstack build, runtime, typecheck, test, and deployment failures, then prepare safe shipping steps.

Skill by Emadgnia

IndexedMIT
Write a review

Chalk Labs

Need help deploying fullstack-ship-troubleshooter?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/emadgnia-fullstack-ship-troubleshooter

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Diagnose and fix fullstack build, runtime, typecheck, test, and deployment failures, then prepare safe shipping steps. Use when users provide error logs, failing commands, local run issues, emulator problems, or ask to commit/push/deploy after fixes (especially JavaScript/TypeScript, Expo, Firebase, Vercel, and monorepo workflows).

Use cases: testing, devops, cloud

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found
Runs as
Shell scripts

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/fullstack-ship-troubleshooter

What's inside

Skill name
fullstack-ship-troubleshooter
Description
Diagnose and fix fullstack build, runtime, typecheck, test, and deployment failures, then prepare safe shipping steps. Use when users provide error logs, failing commands, local run issues, emulator problems, or ask to commit/push/deploy after fixes (especially JavaScript/TypeScript, Expo, Firebase, Vercel, and monorepo workflows).
License
MIT
Instructions
52 lines in SKILL.md · view on GitHub

Before installing

  • Ships executable scripts

Files (5)

  • SKILL.md
  • openai.yaml · agents/
  • diagnostic-sequence.md · references/
  • ship-checklist.md · references/
  • preflight_snapshot.sh · scripts/

SKILL.md (first lines)

# Fullstack Ship Troubleshooter

Use this skill to move from failure logs to a verified, shippable state.

## Triage Workflow

1. Reproduce the failure exactly with the user command.
2. Capture environment and repo snapshot.
3. Isolate root cause to one layer:
   - dependency/toolchain
   - configuration/environment
   - code logic/regression
   - integration/deployment
4. Apply minimal, scoped fix.
5. Re-run failing command and adjacent checks.
6. Prepare ship checklist (without committing or deploying unless explicitly requested).

Use `scripts/preflight_snapshot.sh` for quick environment and repo diagnostics.

## Root Cause Heuristics

- Dependency errors (`MODULE_NOT_FOUND`, unresolved import, peer mismatch): verify lockfile + package manager + workspace boundaries first.
- Runtime config errors (env keys, endpoints, auth): validate required variables and environment target.
- Type/lint failures: fix highest-signal errors first, then rerun targeted command.
- Emulator/service startup issues: verify local ports, required emulators/services, and config paths.
- Deployment failures: separate build errors from provider config and permission errors.

## Verification Standard

At minimum, capture:

- failing command (before)
- fix summary
- passing command (after)
- remaining known issues (if any)

Prefer task-local verification before broad suite runs when time is constrained.

## Safe Shipping Rules

- Do not commit/push/rebase/switch branches unless explicitly asked.
- Do not deploy without explicit approval.
- Provide rollback notes for non-trivial changes.

Use [references/ship-checklist.md](references/ship-checklist.md) before any shipping action.

## References

- [references/diagnostic-sequence.md](references/diagnostic-sequence.md)
- [references/ship-checklist.md](references/ship-checklist.md)

From Emadgnia/claude-agent-skills, MIT.

More from Emadgnia/claude-agent-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Feb 28, 2026 (8 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

More from Emadgnia

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get fullstack-ship-troubleshooter running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying fullstack-ship-troubleshooter?

CallGet help
Cite this page

fullstack-ship-troubleshooter skill. Agent Mart. https://agentmart.dev/skills/emadgnia-fullstack-ship-troubleshooter (last updated 2026-10-24)