status
Paved command paved.status. Inspect Paved setup, diagnostics and open runs, then offer safe repairs. Use when checking readiness or deciding whether a reported Paved problem needs repair.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- status
- description
- Paved command paved.status. Inspect Paved setup, diagnostics and open runs, then offer safe repairs. Use when checking readiness or deciding whether a reported Paved problem needs repair.
03 SKILL.md 正文
<!-- Generated by Paved plugin paved@2.29.0 from paved.status; edit Paved Core instead. -->
Paved status command (paved.status)
Inspect Paved setup, diagnostics and open runs, then offer safe repairs. Use when checking readiness or deciding whether a reported Paved problem needs repair.
Input: No arguments; answer a repair decision with --answer. Output: Consumer inspection, actionable diagnostics, open runs, and repair decisions. Required lifecycle: UNINITIALIZED, INITIALIZED, RESOLVED, GENERATED, VALIDATED, READY, STALE, INCOMPATIBLE, BROKEN Required context: .paved/manifest.yaml, .paved/paved.lock Required capabilities: none declared Allowed side effects: none unless the user answers a repair decision, the repair the user chose
Execution contract
- Invoke
node "<plugin root>/scripts/paved.mjs" status --jsonfrom the repository root, passing the user's command inputs as supported CLI arguments. The launcher loads the pinned project-local runtime and returns the canonical structured result.<plugin root>is the installed Paved plugin directory, two directories above this SKILL.md. Always run the launcher from the repository being worked on, never from the plugin directory. - Follow the structured result's status, diagnostics, evidence, and next action. When
data.remediationnames a Paved command, run it right away, present any decisions it returns, then repeat the original command. Stop only when the runtime blocks on something it cannot remediate.
Failure behavior
- Missing and invalid state is reported without writes.
- No repair is applied without the user's answer.
- If a required ToolImplementation or runtime is unavailable, stop and explain the missing prerequisite. Never infer or execute a command from repository scripts.
- Do not edit human-owned Paved state or bypass lifecycle, ownership, approval, or verification gates.
Conversational contract
- Invoke the command. If it returns
"status": "awaiting_input", it is waiting on the user. - Present every decision in
decisions[]to the user: what Paved detected, what remains to decide, why it matters, the options, Paved's recommendation and its evidence. - Collect the user's answer. Do not answer on their behalf.
- Resume the same command with
--answer <decision-id>=<value> --answered-by <identity>, repeating--answeronce per value for a multi-choice decision. - Present the result.
Follow core.decisions.decisions for the full interaction protocol and its prohibitions.
04 同仓库更多 Skills
sample-skill
Does a sample task. Use when a sample is needed.
unexplained-contract
Does a sample task. Use when a sample is needed.
shell-block
Does a sample task. Use when a sample is needed.
project-identifier
Does a sample task. Use when a sample is needed.
oversized
Does a sample task. Use when a sample is needed.
no-activation
Does a sample task.