Menu

Individual skill

fix

0upvotes

Diagnose and fix a failing Hatchable deploy or a broken deployed app. Use when a Hatchable deploy is rejected, a deployed app errors, or the user reports their Hatchable app is broken.

skills/fix/SKILL.md

Read pinned source

Source commit ef6f5b8dceed3fab1037ad007f46eaa31c4d3c04

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
Yes
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
2
Repository last updated
Sep 24, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Fix a Hatchable deploy

Investigate and fix: $ARGUMENTS

Use the Hatchable MCP tools (the `hatchable` server bundled with this plugin). If the first tool call returns an authentication error, stop and tell the user: run `/mcp`, pick **hatchable**, sign in, then ask again. Do not guess at the cause from memory when the platform can tell you the answer.

Work the problem in this order:

1. Identify the project (`list_projects` / `search_projects` if the user didn't name one).
2. **Rejected deploy:** run `dry_run_deploy` and read every error. Each names the unsupported pattern and its supported replacement. Call `read_skill('debug-a-failing-deploy')` for the canonical triage path.
3. **Deployed but broken:** `view_logs` for runtime errors, `get_deployment` for the last deploy's status, `get_schema` plus `execute_sql` to check data-shape assumptions.
4. Fix with `patch_file` or `write_files`, then `dry_run_deploy`, then `deploy`.
5. Verify against the live URL before declaring it fixed, and summarize the root cause in one line.
Back to top