Complete Profile Reference

🚀Complete Profile Reference

20 Resolver Profiles

See every resolver profile defined by Custy, where it is used, and the concrete steps it expands into.

CommandPIPELINE_PROFILES

📦Category

Pipeline Reference

🚀Quick Command

profile name -> expanded registered steps

---

public profilesdirect-command profilesinternal profiles

---

🪄

Resolver Profiles

20

💻

Public Run Names

6

🛡️

Nested Validation Profiles

4

📄

Source

app/core/pipeline/profiles.py

Overview

PIPELINE_PROFILES is Custy's complete resolver catalog. A profile is a named step definition, not automatically a public CLI value. Some profiles are accepted by custy run, some are selected internally by focused commands, and some exist only to compose larger profiles.

🛡️Resolver profile does not mean public Run profile

Only commit, tag, push, dev, release, and full are accepted by the current typed custy run argument. For example, validate is a real resolver profile used by custy validate, but custy run validate is not currently a supported public invocation.

---

Profile Catalog

ℹ️All Resolver Profiles

Step counts use the fully expanded profile, including nested validation profiles.

commit · 17 steps	Public Run + direct command. custy run commit and custy commit.
tag · 13 steps	Public Run + direct command. custy run tag and custy tag.
push · 3 steps	Public Run + direct command. custy run push and custy push.
dev · 13 steps	Public Run. custy run dev daily commit-and-branch-push composition without release side effects.
release · 25 steps	Public Run. custy run release complete publication flow.
full · 26 steps	Public Run. custy run full Release plus workflow finalization.
validate · 10 steps	Direct command. custy validate readiness checks.
changelog · 1 step	Direct command. custy changelog generate.
apply_version · 5 steps	Direct command. custy version update.
backup_commit_message · 1 step	Direct command. custy backup commit.
backup_tag_message · 1 step	Direct command. custy backup tag.
backup_all · 2 steps	Direct command. custy backup all.
cleanup_backups · 1 step	Direct command. custy cleanup backups and the backup part of custy cleanup all.
cleanup_branches · 1 step	Direct command. custy cleanup branches and the branch part of custy cleanup all.
init · 1 step	Direct command. custy init.
validate-sub-repo · 1 step	Nested internal. Reusable repository validation prefix.
validate-sub-pre-commit · 5 steps	Nested internal. Reusable message-provider and commit-hook readiness group.
validate-sub-pre-tag · 3 steps	Nested internal. Reusable version and tag-message validation group.
validate-sub-pre-push · 1 step	Nested internal. Reusable remote validation prefix.
cleanup_all · 2 steps	Defined aggregate. cleanup_backup_step plus cleanup_branches_step. The current custy cleanup all command invokes the two focused profiles separately instead of resolving this aggregate.

---

Exact Public Run Expansions

These are the concrete step orders returned when each public profile is resolved by itself. Single-profile resolution preserves this declared order.

commit — 17 steps

text

01  ensure_git_repo_step
02  ensure_staged_changes_step
03  ensure_commit_validation_provider_step
04  ensure_commit_hook_policy_step
05  ensure_commit_message_file_step
06  ensure_commit_message_file_exists_step
07  prepare_version_step
08  workflow_init_step
09  generate_artifacts_step
10  edit_files_step
11  validate_edited_step
12  apply_version_step
13  generate_changelog_step
14  backup_commit_message_files_step
15  cleanup_backup_step
16  stage_step
17  commit_step

tag — 13 steps

text

01  ensure_git_repo_step
02  ensure_version_file_step
03  ensure_tag_message_file_step
04  ensure_tag_message_file_exists_step
05  prepare_version_step
06  workflow_init_step
07  prepare_tag_message_step
08  generate_artifacts_step
09  edit_files_step
10  apply_version_step
11  backup_tag_message_files_step
12  cleanup_backup_step
13  tag_step

push — 3 steps

text

01  ensure_git_repo_step
02  ensure_remote_exists_step
03  push_step

dev — 13 steps

text

01  ensure_git_repo_step
02  ensure_commit_validation_provider_step
03  ensure_commit_hook_policy_step
04  ensure_commit_message_file_step
05  ensure_commit_message_file_exists_step
06  ensure_remote_exists_step
07  edit_files_step (include_tag=false)
08  validate_edited_step
09  backup_commit_message_files_step
10  cleanup_backup_step
11  stage_step
12  commit_step
13  push_step (include_tag=false)

release — 25 steps

text

01  ensure_git_repo_step
02  ensure_staged_changes_step
03  ensure_commit_validation_provider_step
04  ensure_commit_hook_policy_step
05  ensure_commit_message_file_step
06  ensure_commit_message_file_exists_step
07  ensure_version_file_step
08  ensure_tag_message_file_step
09  ensure_tag_message_file_exists_step
10  ensure_remote_exists_step
11  prepare_version_step
12  workflow_init_step
13  prepare_tag_message_step
14  generate_artifacts_step
15  edit_files_step
16  validate_edited_step
17  apply_version_step
18  generate_changelog_step
19  backup_commit_message_files_step
20  backup_tag_message_files_step
21  cleanup_backup_step
22  stage_step
23  commit_step
24  tag_step
25  push_step

full — 26 steps

text

01  ensure_git_repo_step
02  ensure_staged_changes_step
03  ensure_commit_validation_provider_step
04  ensure_commit_hook_policy_step
05  ensure_commit_message_file_step
06  ensure_commit_message_file_exists_step
07  ensure_version_file_step
08  ensure_tag_message_file_step
09  ensure_tag_message_file_exists_step
10  ensure_remote_exists_step
11  prepare_version_step
12  workflow_init_step
13  prepare_tag_message_step
14  generate_artifacts_step
15  edit_files_step
16  validate_edited_step
17  apply_version_step
18  generate_changelog_step
19  backup_commit_message_files_step
20  backup_tag_message_files_step
21  cleanup_backup_step
22  stage_step
23  commit_step
24  tag_step
25  push_step
26  finalize_step

For friendly explanations of every Dev, Release, and Full step, continue to the Development Pipeline, Release Pipeline, and Full Pipeline.

---

Direct-Command and Support Expansions

Validation and release support

text

validate — 10 steps
01 ensure_git_repo_step
02 ensure_remote_exists_step
03 ensure_version_file_step
04 ensure_staged_changes_step
05 ensure_commit_validation_provider_step
06 ensure_commit_hook_policy_step
07 ensure_commit_message_file_step
08 ensure_commit_message_file_exists_step
09 ensure_tag_message_file_step
10 ensure_tag_message_file_exists_step

changelog — 1 step
01 generate_changelog_step

apply_version — 5 steps
01 ensure_git_repo_step
02 ensure_version_file_step
03 prepare_version_step
04 prepare_tag_message_step
05 apply_version_step

Backup, cleanup, and initialization

text

backup_commit_message — 1 step
01 backup_commit_message_files_step

backup_tag_message — 1 step
01 backup_tag_message_files_step

backup_all — 2 steps
01 backup_commit_message_files_step
02 backup_tag_message_files_step

cleanup_backups — 1 step
01 cleanup_backup_step

cleanup_branches — 1 step
01 cleanup_branches_step

cleanup_all — 2 steps
01 cleanup_backup_step
02 cleanup_branches_step

init — 1 step
01 Initialization_custy_step

Nested validation profiles

text

validate-sub-repo
01 ensure_git_repo_step

validate-sub-pre-commit
01 ensure_staged_changes_step
02 ensure_commit_validation_provider_step
03 ensure_commit_hook_policy_step
04 ensure_commit_message_file_step
05 ensure_commit_message_file_exists_step

validate-sub-pre-tag
01 ensure_version_file_step
02 ensure_tag_message_file_step
03 ensure_tag_message_file_exists_step

validate-sub-pre-push
01 ensure_remote_exists_step

---

ℹ️Expansion order and merged order are different concepts

The lists above show one profile resolved by itself. When two or more profiles are selected, Custy combines them, removes repeated step names, and sorts the result using STEP_ORDER. See Step Priority and Ordering for the complete algorithm and priority table.

---

Continue

🚀Related Commands

Commands commonly used together with this command.

Step Priority and Ordering

Understand all 28 priority entries and merged-profile sorting.

Public Profiles

Choose among the six supported Run names.

Custom Composition

See how public profiles merge and deduplicate.

Step System

Review registration, construction, context, and contributor rules.