proofline

Purpose

The user-facing /proofline entry point.

Source Skill purpose

When to use it

Use proofline to install the workflow in a project, inspect its enforcement and status, or begin and resume a task through the user-facing command. Local utility subcommands run through the proofline CLI. Task, design, review, audit, debug, knowledge and delivery requests pass control to proofline-lead, which follows the run's lifecycle and dispatches the specialist roles. This entry point does not itself implement the requested change; it selects the right workflow and reports the command's result.

The utility entry points report what the CLI actually printed. Installation and upgrade preserve user-edited files, and delivery remains a separate approved workflow step.

Source Skill purpose

How it works

The skill definition states no numbered steps.

Source Skill definition

Key rules

  • Leave product code, verdicts, approvals and waivers to the lead and specialists working within a run.

    Source Hard rules

  • Installation and upgrade merge files without overwriting user modifications or changing global Git configuration.

    Source Hard rules

  • Keep commits, pushes and pull requests out of installation, upgrade and cleaning; delivery requires explicit approval.

    Source Hard rules

  • Use the user's language for messages, while files and identifiers remain in English.

    Source Hard rules

Output and gate

Output

The skill definition states no output.

Source Skill definition

Gate

The skill definition states no gate rule.

Source Skill definition

Source

Source Skill definition

← All skills