Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

automazeio

@automazeio source repo

4 published skills

  1. ▌
    Envapor · automazeio
    Manage encrypted .env files in Git using Envapor (transparent AES-256-GCM encryption via clean/smudge filters). Use when a repository contains ENC[...] values in .env files, when asked to encrypt .env secrets in Git, onboard to or set up an Envapor repository, rotate Envapor keys, or debug Envapor filter, hook, or decryption issues.
    0
    installs
  2. ▌
    Mental Model · automazeio
    Maintains a living mental model of the codebase. Read mental-model.md before making changes, update it when discovering new patterns or behaviors.
    0
    installs
  3. ▌
    Proof · automazeio bundle
    Capture test runs as shareable, replayable evidence artifacts — not just running tests, but documenting and sharing that they passed. Works from any language: standalone binary, TypeScript, Python, or Go SDKs. Use cases: attach replayable terminal output to a PR instead of a screenshot; generate a markdown proof report for PR descriptions or tickets; record a browser test as a self-contained HTML video; record an iOS Simulator or Android emulator screen during XCUITest or Espresso runs, with automatic tap indicator overlays; export terminal recordings as MP4 for inline embedding in Linear or Jira; or tie passing tests to a git commit as an audit trail. Trigger on phrases like "attach evidence to PR", "save test output as artifact", "replayable test recording", "proof report", "record my test run", "record iOS simulator", "record Android emulator", "capture mobile tests", "export as video", "embed in Linear", "embed in Jira", or when the user mentions proof, @automaze/proof, or automaze-proof directly.
    0
    installs
  4. ▌
    Ccpm · automazeio bundle
    CCPM - spec-driven project management: PRD → Epic → GitHub Issues → parallel agents → shipped code. Use this skill for anything in the software delivery lifecycle: writing a PRD ('write a PRD for X', 'let's plan X', 'scope this out'), parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub ('sync the X epic', 'push tasks to github'), starting work on an issue ('start working on issue N', 'let's work on issue N'), analyzing parallel work streams, running standups ('standup', 'run the standup'), checking status ('what's next', 'what's blocked', 'what are we working on'), closing issues, or merging an epic. Use ccpm any time the user is talking about shipping a feature, managing work, or tracking progress — even if they don't say 'ccpm' or 'PRD'. Do NOT use for: debugging code, writing tests, reviewing PRs, or raw GitHub issue/PR operations with no delivery context.
    1
    install