agentmods.dev

feature-flow

A command that coordinates a feature’s Git workflow across GitHub, GitLab, or Forgejo, including branches, issues, commits, checks, and merging.

In plain words
What is it for?
Use it to turn staged changes or an issue into a branch, issue work, quality checks, a commit, and a merge request.
Why use it?
It brings repeated repository tasks into one guided process and can validate changes with linting and tests.

Command

16 7d ago A scan 24 tokens original MIT
View the source file sgaunet/claude-plugins
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/sgaunet/claude-plugins/feature-flow
Clone the repo
git clone --depth 1 https://github.com/sgaunet/claude-plugins
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,261 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.04261
Opus 5 $0.00012 $0.02131
Sonnet 5 $0.00005 $0.00852
Haiku 4.5 $0.00002 $0.00426

Measured 2d ago against content hash a506acf6d735, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

feature-flow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/software-engineering/commands/feature-flow.md · 347 lines

How it starts

The opening of the file, as written. The whole thing — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Feature Flow Command

Orchestrate a complete git workflow for feature development. Two modes:

  1. Staged Changes Mode (default): Analyze staged changes → branch → create issue → commit
  2. Issue Mode (#<number>): Retrieve issue → validate relevance → branch → implement → lint → test → verify → commit → merge

Automates repetitive workflow setup (branching, issues, commits, quality checks, merge requests).

Mode Detection

Route based on $argument: first positional argument matching #<number> or bare <number> → Issue Mode; otherwise → Staged Changes Mode.

Issue Mode examples: /feature-flow #42, /feature-flow 42 --squash Staged Mode examples: /feature-flow, /feature-flow add user auth, /feature-flow --skip-issue

Staged Changes Mode (5 Phases)

Phase 1: Discovery & Validation (Automatic)

Execute parallel git commands: git status and git diff --staged

Detect Repository Host: Use the detect-repo-host skill to identify the hosting service (GitHub, GitLab, or Forgejo) and extract owner/repo details.

Analysis steps:

  1. Analyze staged changes:

    • Extract file paths, extensions, and types
    • Determine change type: new files → feat, test+fixes → fix, docs only → docs, structural → refactor, build/config → chore
    • Extract primary scope from directory (e.g., src/api/ → api, internal/auth/ → auth)

  2. Generate proposed branch name:

    • Format: <type>/<scope>-<description> (kebab-case, 2-4 words)
    • Types: feat, fix, refactor, docs, chore, test, perf, ci
    • Examples: feat/api-user-profile, fix/auth-jwt-validation, docs/readme-update

Error handling:

  • No staged changes → Abort: "No staged changes found. Stage files with 'git add' first."
  • Repository host detection fails → The detect-repo-host skill provides detailed error messages

Phase 2: Branch Creation (User Confirmation)

Parse flags: --skip-branch or -b → skip this phase.

If not skipped:

Read the full file on GitHub · 347 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 347 lines · 24 tokens per session scan A a506acf6d735

Subscribe to this mod's changes

feature-flow is a command published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 7d ago), licensed MIT. It adds 24 tokens to every session and 4,261 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

CommitsGit and workflowai-agentsclaude-codeclaude-code-marketplaceclaude-code-pluginsdeveloper-tools
Related

Other commands, from other repositories

commit

Create well-formatted commits with conventional commit messages and emojis.

NikiforovAll/claude-code-rules · 4 tokens

security-audit-static

Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.

phuryn/pm-skills · 29 tokens

performance-audit-static

Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.

phuryn/pm-skills · 33 tokens

document-app

Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.

phuryn/pm-skills · 44 tokens

analyze-test

Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations.

phuryn/pm-skills · 20 tokens

plan-okrs

Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.

phuryn/pm-skills · 17 tokens