plane-cli-tool_skill

This skill helps you manage Plane.so projects, issues, and labels via CLI by executing common workflows with clear JSON outputs.

Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill plane-cli-tool

_meta.json277 B
SKILL.md2.8 KB

Overview

This skill provides a CLI interface to Plane.so for creating, updating, and managing issues, projects, states, labels, and pages. It produces machine-friendly JSON by default and supports interactive configuration, environment variable settings, and scripted workflows. Use it to automate project-management tasks from the terminal or CI agents.

How this skill works

Install the CLI and run an interactive config wizard or set environment variables (PLANE_API_KEY, PLANE_WORKSPACE_SLUG, PLANE_BASE_URL, PLANE_PROJECT). Commands follow a resource/verb pattern (e.g., plane issues create, plane projects list) and output JSON suitable for piping to tools like jq. Many flags accept '-' to read from stdin; destructive operations require explicit confirmation when not running in a TTY.

When to use it

Create, list, or update issues and their comments from scripts or CI pipelines.
Manage project metadata: projects, states, and labels without opening the Plane web UI.
Automate status transitions (move issues between states) as part of deployments.
Bulk export or backup project items in JSON for archiving or processing.
Integrate git hooks or CI steps that post updates or comments to Plane issues.

Best practices

Keep API key and defaults in env vars or the config file to avoid repeating flags.
Prefer JSON output for automation; use --pretty only for interactive viewing.
Use --all with care (capped at 1000); paginate in scripts to avoid large responses.
Read command help with --help for exact flags; do not assume option names.
Always confirm destructive actions; require interactive approval or pass --yes in controlled agent contexts.

Example use cases

Create a new issue from a CI job: plane issues create --title 'Build failed' --body -
Move an issue to In Progress after starting work: plane issues update <id> --state <state-id>
Add deployment notes as an issue comment using stdin: git diff HEAD~1 | plane issues comment add <id> --body -
List all project states to map workflows programmatically: plane states list --project <pid>
Export issues for backup or analytics by piping JSON to jq or another processor.

FAQ

Set PLANE_API_KEY, PLANE_WORKSPACE_SLUG, PLANE_BASE_URL, and PLANE_PROJECT environment variables or pass flags on each command.

Can I script destructive commands?

Yes, but deletes require --yes in non-TTY contexts; include explicit confirmation in automation to avoid accidental data loss.