Run any Skill in Manus with one click

$pwd:

elixir-clause-grouping

Name: Elixir Clause Grouping
Author: blockscout

// Use when refactoring Elixir multi-clause functions, extracting helper functions, or fixing Credo readability warnings caused by placing `defp` helpers between clauses of the same function. Keeps function clauses contiguous and moves helpers below the full clause group.

Run Skill in Manus

$ git log --oneline --stat

stars:4,552

forks:3,076

updated:April 9, 2026 at 12:45

SKILL.md

readonly

name	elixir-clause-grouping
description	Use when refactoring Elixir multi-clause functions, extracting helper functions, or fixing Credo readability warnings caused by placing `defp` helpers between clauses of the same function. Keeps function clauses contiguous and moves helpers below the full clause group.

Overview

In Elixir modules, all clauses of the same function should stay together. Inserting a defp helper between clauses of a def or defp makes the function harder to read and can trigger Credo readability warnings. When shared logic needs to be extracted, keep the original clause group contiguous and place the helper after the full group.

When to Use

When refactoring a multi-clause def or defp
When extracting duplicated logic from multiple function clauses
When addressing Credo warnings about clause grouping or readability
When editing controller, view, or context modules with several clauses of the same function
During review when a helper was added in the middle of another function's clauses

Core Rule

Keep all clauses of the same function contiguous
Do not place defp helpers between clauses of another function
Extract shared logic into a helper placed after the full clause group

Anti-Pattern

def decoded_input_data(%Transaction{to_address: nil}, _, _, _, _), do: {:error, :no_to_address}

defp decode_input_data_with_fallback(data, abi, input, hash, skip_sig_provider?, options, methods_map, abi_map) do
  ...
end

def decoded_input_data(%Transaction{to_address: %NotLoaded{}}, _, _, _, _), do: {:error, :contract_not_verified, []}

This splits the decoded_input_data/5 clause group and makes the function harder to scan.

Preferred Pattern

def decoded_input_data(%Transaction{to_address: nil}, _, _, _, _), do: {:error, :no_to_address}

def decoded_input_data(%Transaction{to_address: %NotLoaded{}}, _, _, _, _), do: {:error, :contract_not_verified, []}

def decoded_input_data(%Transaction{to_address: %{smart_contract: smart_contract}} = transaction, skip_sig_provider?, options, methods_map, abi_map) do
  ...
end

defp decode_input_data_with_fallback(data, abi, input, hash, skip_sig_provider?, options, methods_map, abi_map) do
  ...
end

Refactoring Checklist

Identify every clause of the function being edited.
Keep those clauses adjacent to each other.
Extract shared logic only after the full clause group.
Re-check that no unrelated def or defp appears inside the group.
Run formatting after the refactor.

Notes

This applies to both public and private multi-clause functions.
If a helper is only used by one clause group, place it immediately after that group.
Preserving clause grouping is preferred even when the extracted helper is small.

related-skills.json

same repository

openapi-spec.md

from "blockscout/blockscout"

Create, adjust, or inspect OpenAPI declarations for Blockscout API v2 endpoints. Use this skill whenever the user asks to: add an OpenAPI spec to an endpoint that lacks one, update a spec after controller/view changes, audit or fix an existing OpenAPI declaration, or work with open_api_spex annotations in the Blockscout codebase. Also trigger when the user mentions 'swagger', 'openapi', 'open_api_spex', 'API spec', 'API schema', or 'operation macro', or when debugging failures like 'response schema mismatch', 'CastAndValidate rejection', 'json_response validation error', 'Unexpected field', or extra/missing keys in API responses.

2026-05-084.6k

update-common-blockscout-env.md

from "blockscout/blockscout"

Ensure every newly introduced environment variable is also added to docker-compose/envs/common-blockscout.env so local Docker setups stay aligned with runtime configuration.

2026-04-074.6k

with-to-case-refactor.md

from "blockscout/blockscout"

Replace `with` expressions that contain only a single `<-` clause and an `else` branch with a `case` expression. This addresses the Credo warning "with contains only one <- clause and an else branch, consider using case instead" and produces cleaner, more idiomatic Elixir code.

2026-04-064.6k

elixir-credo-predicate-naming.md

from "blockscout/blockscout"

Use when working on Elixir code with Credo predicate naming warnings, boolean helper functions, or renaming functions that start with is_. Prevents violations like: Predicate function names should not start with 'is' and should end in a question mark.

2026-03-104.6k

alias-nested-modules.md

from "blockscout/blockscout"

Define module aliases at the top of the file instead of using fully qualified nested module names in function bodies. Improves code readability and maintainability while addressing Credo style warnings.

2026-03-064.6k

alphabetically-ordered-aliases.md

from "blockscout/blockscout"

Ensure that aliases are alphabetically ordered within their groups to maintain consistent code style and address Credo readability warnings.

2026-03-064.6k

package.json

"author": "blockscout"

"repository": "blockscout/blockscout"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	elixir-clause-grouping
description	Use when refactoring Elixir multi-clause functions, extracting helper functions, or fixing Credo readability warnings caused by placing `defp` helpers between clauses of the same function. Keeps function clauses contiguous and moves helpers below the full clause group.

Overview

When to Use

When refactoring a multi-clause def or defp
When extracting duplicated logic from multiple function clauses
When addressing Credo warnings about clause grouping or readability
When editing controller, view, or context modules with several clauses of the same function
During review when a helper was added in the middle of another function's clauses

Core Rule

Keep all clauses of the same function contiguous
Do not place defp helpers between clauses of another function
Extract shared logic into a helper placed after the full clause group

Anti-Pattern

def decoded_input_data(%Transaction{to_address: nil}, _, _, _, _), do: {:error, :no_to_address}

defp decode_input_data_with_fallback(data, abi, input, hash, skip_sig_provider?, options, methods_map, abi_map) do
  ...
end

def decoded_input_data(%Transaction{to_address: %NotLoaded{}}, _, _, _, _), do: {:error, :contract_not_verified, []}

This splits the decoded_input_data/5 clause group and makes the function harder to scan.

Preferred Pattern

def decoded_input_data(%Transaction{to_address: nil}, _, _, _, _), do: {:error, :no_to_address}

def decoded_input_data(%Transaction{to_address: %NotLoaded{}}, _, _, _, _), do: {:error, :contract_not_verified, []}

def decoded_input_data(%Transaction{to_address: %{smart_contract: smart_contract}} = transaction, skip_sig_provider?, options, methods_map, abi_map) do
  ...
end

defp decode_input_data_with_fallback(data, abi, input, hash, skip_sig_provider?, options, methods_map, abi_map) do
  ...
end

Refactoring Checklist

Identify every clause of the function being edited.
Keep those clauses adjacent to each other.
Extract shared logic only after the full clause group.
Re-check that no unrelated def or defp appears inside the group.
Run formatting after the refactor.

Notes

This applies to both public and private multi-clause functions.
If a helper is only used by one clause group, place it immediately after that group.
Preserving clause grouping is preferred even when the extracted helper is small.

elixir-clause-grouping

Overview

When to Use

Core Rule

Anti-Pattern

Preferred Pattern

Refactoring Checklist

Notes

More from this repository

More from this repository

Overview

When to Use

Core Rule

Anti-Pattern

Preferred Pattern

Refactoring Checklist

Notes