ferrosadb

CI/CD pipelines with GitHub Actions, immutable artifacts, quality gates, and safe deploys. Use when setting up CI/CD, configuring build pipelines, adding deployment automation, or troubleshooting failed builds.

Manages the full git commit lifecycle — branches, pre-commit hooks, change grouping, conventional messages. Use when asked to 'commit' or 'save changes'. Never commits to main.

Create or refactor agent skills with progressive disclosure. Use when writing skills, restructuring skills for context efficiency, or creating subagents, rules, hooks, and workflows.

Initializes and manages pre-commit hooks for monorepos. Use when setting up pre-commit hooks, adding linting/formatting to git workflow, or managing .pre-commit-config.yaml.

Scaffolds a new project with best-practice structure. Use when starting a project, creating an app, or initializing a codebase. Supports Python, Elixir, Rust, Go, and Node/TypeScript.

Pushes commits to remote and auto-creates a GitHub PR with structured template. Use when asked to 'push', 'create a PR', or 'open a pull request'. Returns the PR URL.

Python with pytest, type hints, pandas/NumPy, and virtual environments. Use when writing Python code, configuring projects, building data pipelines, or debugging Python applications.

Discovers all local branches, tests each, pushes passing ones as PRs, monitors CI, and cleans up superseded branches. Use when asked to 'ship it', 'push everything', or 'clean up branches'.

Force a Ferrosa Memory consolidation pass at the end of a productive session so the dream cycle (edges, scenes, profiles) runs now instead of on the idle timer. Use at wrap-up, when the user says "that's it for now", or before a long break.

Capture deferred/follow-up work to the forge task board so it isn't lost. Use when you surface work you won't do now — out-of-scope items, prerequisites, follow-ups, "leave for later", known gaps. Pairs with /whats-next and /roadmap.

Restore working context from Ferrosa Memory at the start of a session (or after /clear) before doing anything else. Use at session start, after compaction, or when resuming work on a repo.

Build a roadmap for a repo by combining deferred work from the forge task board with a live TODO/FIXME scan of the repo, synthesized into themed, prioritized Now/Next/Later. Use when asked for a repo's roadmap, backlog, or debt plan.

Declare a time-bounded fact or temporary constraint in Ferrosa Memory (valid_from / valid_until). Use when something only holds for a window — a deadline, code freeze, deprecation, or planned-future change — so search surfaces it only while it is valid.

Answer "what's next?" by surfacing open deferred/follow-up work for the current repo from the forge task board, ranked. Use when asked what to work on next, what's outstanding, or to resume work.

Apply Forge workflow discipline with small checklists, bounded attempts, acceptance criteria, and verification gates.

Use when driving development from a Google Sheet of bugs — pull open rows into the forge task board, work them, and push fix status/version/notes back to the sheet without clobbering the owner's cells.