Deploy to Hostinger via SSH+Git with key management, post-receive hooks, and rollback strategy. Alternative to FTP/SFTP for automated deployments. [EXPLICIT] Trigger: "SSH deploy", "Hostinger SSH", "git push deploy", "remote deployment", "SFTP"
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdtemplates/output.docx.mdtemplates/output.htmlSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
"Push to deploy. If it breaks, push to revert."
Deploys to Hostinger shared hosting via SSH+Git as an alternative to FTP/SFTP. Sets up SSH key authentication, bare Git repository on the server with post-receive hook for automatic deployment, and rollback via git revert. Covers key management, connection security, and .ssh/config for convenience. Falls back to SFTP if SSH is unavailable on the Hostinger plan. [EXPLICIT]
ssh user@host "git --version")hostinger-deployment skill (FTP/SFTP)public_htmlgit revert HEAD + push triggers automatic rollbackssh-keygen -t ed25519 -C "deploy@jm-adk" -f ~/.ssh/hostinger_deploy
~/.ssh/authorized_keys)~/.ssh/config:
Host hostinger
HostName {server-ip}
Port 65002
User {username}
IdentityFile ~/.ssh/hostinger_deploy
StrictHostKeyChecking accept-new
ssh hostinger "echo ok"ssh hostinger "git init --bare ~/deploy.git"
ssh hostinger "cat > ~/deploy.git/hooks/post-receive << 'HOOK'
#!/bin/bash
GIT_WORK_TREE=~/public_html git checkout -f main
echo \"Deployed at \$(date)\"
HOOK
chmod +x ~/deploy.git/hooks/post-receive"
git remote add deploy hostinger:~/deploy.git
git push deploy main
GIT_WORK_TREE=~/public_html git checkout -f main
cd ~/public_html && npm ci && npm run build
ssh hostinger "echo ok" succeeds without password promptgit push deploy main triggers automatic deploymenthttps://yourdomain.com after pushgit revert HEAD && git push deploy main.ssh/config file permissions are correct (600)git revert + push works.ssh/config configured for convenience| Anti-Pattern | Why It's Bad | Do This Instead |
|---|---|---|
| Password-based SSH login | Insecure, can't automate | Use Ed25519 key pair |
| Storing SSH key in repo | Credential exposure | Use ~/.ssh/ with proper permissions |
| No rollback plan | Broken deploys stay broken | Always test git revert + push |
| Ignoring port number | Hostinger uses non-standard SSH port | Check panel for correct port (often 65002) |
| Skip connection test | Discover errors at deploy time | Always ssh host "echo ok" first |
hostinger-deployment — FTP/SFTP deployment (fallback)firebase-deployment — Firebase Hosting deployment (alternative target)github-actions-ci — Automate SSH deployment in CI pipelinedeployment-checklist — Pre-deploy quality gatesExample invocations:
| Scenario | Handling |
|---|---|
| Empty or minimal input | Request clarification before proceeding |
| Conflicting requirements | Flag conflicts explicitly, propose resolution |
| Out-of-scope request | Redirect to appropriate skill or escalate |