agentleFS
Sign inStart free
mustafahasanainmustafahasanain/frappe-workflow/skills/deployment/SKILL.md

deployment

Skill0 starsChanged 3 months agoMITView on GitHub

Optional demo-server deployment - explicit confirmation, local and remote preflight, fast-forward-only pull over SSH, minimal required bench commands, and deployed-commit verification.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dependency-management, database and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dkprogSkill

    dependency-management

    Apply when wiring dependencies, integrating external services, or designing interfaces between modules. Ensures loose coupling through dependency injection, interface segregation, and proper abstraction boundaries.

    Also in 3 projects that use this

  • mijunriSkill

    database

    数据库脚本与操作规范。脚本放在 db_scripts 目录，遵循查询优化、事务、安全等实践。

    Also in 3 projects that use this

  • BlockSkill

    debugging

    Debugging guidelines and best practices

    Also in 6 projects that use this

  • AnthropicSkill

    documentation

    Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.

    Also in 5 projects that use this

  • AnthropicSkill

    architecture

    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

    Also in 5 projects that use this

  • pproencaSkill

    refactoring

    Code refactoring best practices based on Martin Fowler's catalog and Clean Code principles. This skill should be used when refactoring existing code, improving code structure, reducing complexity, eliminating code smells, or reviewing code for maintainability. Triggers on tasks involving extract method, rename, decompose conditional, reduce coupling, or improve readability.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Deployment Skill

Deploys the verified task commit to the demo server — only after the user explicitly chooses to. Skipping is a first-class outcome, not a failure.

When to Use

  • The deploy action, or resuming into stage committed.

The Question (always, verbatim, before anything else)

The task has been committed successfully.

Deploy this task to the demo server?

1. Deploy now
2. Skip deployment

No SSH connection is opened before the answer.

  • Skip →

    bin/frappe-workflow state set deployment.required false --json-value
bin/frappe-workflow state set deployment.status skipped
bin/frappe-workflow state set deployment.skip_reason "Skipped by user"
bin/frappe-workflow state transition deployment_skipped --reason "user skipped"

    (use the user's stated reason when they gave one). No SSH, no server commands, no local deployment commands. Done.

  • Deploy now → the procedure below.

Procedure

  1. Config: bin/frappe-workflow deployment validate-config (.claude/deployment.local.json; see the example template).
  2. Local + config/task consistency: bin/frappe-workflow deployment preflight — also prints the exact remote read-only preflight commands (references/deployment-preflight.md).
  3. Remote preflight over SSH per references/ssh-safety.md — read-only.
  4. Fast-forward-only pull; then the minimal bench command set from bin/frappe-workflow deployment required-commands --commit <hash> (references/frappe-command-matrix.md).
  5. Verify and record (references/deployment-verification.md); state transition deployed.

Inputs

  • Stage committed with verified commit.hash; deployment config.

Outputs

  • Deployment record in state (commits before/after, commands, results, timestamp) — secrets never recorded.

Preconditions

  • Explicit "Deploy now" answer this session; both preflights pass.

Stopping Conditions — stop immediately, report, change nothing

Server local changes · unexpected branch · missing remote · missing commit · diverged history · failed bench command · mismatched final commit. Recovery on the server is a human decision, never automatic.

Prohibited

  • Any SSH before the explicit answer.
  • stash / reset / clean / checkout-another-branch / merge commits on the server; discarding server work.
  • Running bench commands the changed files do not require.
  • Printing private keys, passwords, or storing them in config or records.

Shared Rules

git-safety-rules.md, security-rules.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free