Output

🚀Output

Recommended

Learn how Custy reports validation results and what they mean.

Commandcusty validate

📦Category

Validation

🚀Quick Command

custy validate

---

outputvalidationresults

---

Overview

After completing validation, Custy reports whether the project satisfies the requirements needed for subsequent workflows.

Successful validation indicates that the checked prerequisites have been verified successfully.

If validation encounters a problem, execution stops immediately and Custy reports the reason together with guidance for resolving the issue.

---

Typical Output

💻Command Output

Example output produced after running the command.

Successful Validation

All configured validation checks completed successfully.

Terminal

text

✓ Git repository found
✓ Git remote verified
✓ Version file found
✓ Commit message template found
✓ Tag message template found
✓ Repository validation completed

---

💡Notes

The exact output may vary depending on your configuration and enabled validation checks.

Validation Failure

A required validation step failed before the workflow could continue.

Terminal

text

✗ Git repository not found

Hint:
Run git init

---

💡Notes

Validation stops immediately after the first failure and reports the corresponding guidance.

---

Successful Validation

When every validation step succeeds:

• The repository satisfies the configured prerequisites.
• Required project resources are available.
• Workflow-oriented commands may safely continue.
• No repository history is modified.

Successful validation only confirms readiness.

It does not create commits, tags, releases, or modify your project.

---

Validation Failure

When validation fails:

• The current validation step is reported.
• Remaining validation steps are skipped.
• A descriptive message explains the problem.
• A helpful hint is provided whenever possible.

This fail-fast behavior helps identify and resolve problems quickly before attempting more complex workflow operations.

---

💡Read the Hint

Whenever validation fails, read the accompanying hint before retrying.

Most validation failures can be resolved by following the suggested action, such as initializing a Git repository, generating required templates, or staging project changes.

---

Dry Run

When validation is executed as part of a workflow using the global

--dry-run option, Custy reports what would normally happen without performing workflow actions that modify the repository.

This allows you to inspect workflow readiness before executing the actual operation.

---

What's Next?

If validation reports a problem, continue to the Troubleshooting page for guidance on resolving common validation failures.