skills.rest
glowingkitty
glowingkittyCOMMUNITY
Explore all skills by this author →
GitHub

deploy

Automate linting, previewing, committing, and pushing tracked code changes via OpenMates session tooling.

43|2|Updated Jan 25, 2024
Search Tags:#git#linting#commit messages#session management#deploy#CI safety
One-click install
npx skills add https://github.com/glowingkitty/OpenMates --skill deploy-glowingkitty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/glowingkitty/OpenMates/tree/main/.agents/skills/deploy
Command: npx skills add https://github.com/glowingkitty/OpenMates --skill deploy-glowingkitty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents missed steps and inconsistent commits by guiding you through the OpenMates session-based deployment flow with the correct documentation, previews, and guarded push behavior.

Core Features & Use Cases

  • Session-tracked deployment: Uses scripts/sessions.py to lint, commit, and push tracked changes rather than bypassing session tracking.
  • Deployment preview and selective exclusion: Prepares a deploy plan for a specific session and lets you exclude files that shouldn’t be committed.
  • Consistent commit messaging: Enforces a structured commit title/message format aligned with the project’s contribution rules.
  • Failure recovery guidance: Directs you to fix lint errors or handle unrelated hook failures safely using session options.

Quick Start

Run the deploy flow for your active session by loading deployment docs, previewing the planned file list for that session, and then deploying with a compliant title and message.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I lint and commit tracked changes using a session-based deployment flow?▼

To lint and commit tracked changes, run the session deployment flow by loading deploy docs, previewing the file list for your session, and deploying with a compliant title and message.

Can I exclude specific files from a commit during a sessioned push?▼

Yes, you can exclude specific files during a sessioned push. The deployment preview step allows you to review the planned file list for a chosen session and selectively omit files that shouldn't be committed.

Why does my session deployment fail during the linting and committing process?▼

Session deployment fails during linting if code quality checks are not met. You must fix lint errors or safely handle unrelated hook failures using available session options before retrying the push.

Do I need to run raw git commit commands when using session-based code deployments?▼

No, you should avoid raw git commit commands for session-based code deployments. You must use the designated session tooling to ensure linting, structured commit messages, and guarded push behavior are applied.

How are commit message formats enforced for sessioned code changes?▼

Commit message formats are enforced by requiring a structured title and message during the deployment step. This ensures all committed code changes align with the project's documented contribution rules.

What is the best way to safely preview and push code changes without bypassing session tracking?▼

The best way to safely preview and push code changes is to use the prepare-deploy command for a chosen session. This previews the deployment plan and applies guarded push behavior to prevent bypassing session tracking.

Related Skills

Explore More Software Engineering Skills→
vetacreativalaservetacreativalaser

claude-context

Load CLAUDE_PROMPT.md instructions into Claude's session context.

Community
Basic
hdonovan42hdonovan42

dcp

Deploy a project to a VPS, commit changes, and push to the remote repository.

Community
Advanced
avvaleavvale

conventional-commits

Validate commit messages against the Conventional Commits specification.

Official
Basic
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic