.ai/skills/pr-markdown-body-file/SKILL.md
Always edit/create GitHub PR bodies from a markdown file; never inline escaped newlines.
npx skillsauth add nikivdev/flow pr-markdown-body-fileInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when creating or editing pull requests.
\n.--body-file.f pr open edit when available for local file-driven PR editing.Inline escaped newlines are fragile and can produce literal \n text in GitHub PR descriptions.
--body-file is deterministic and reviewable.
cat > /tmp/pr-body.md <<'EOF'
## Summary
- ...
## Scope
- ...
EOF
gh pr create --title "..." --body-file /tmp/pr-body.md
cat > /tmp/pr-body.md <<'EOF'
## Summary
- ...
EOF
gh pr edit <number> --body-file /tmp/pr-body.md
f pr open edit
This opens a local markdown file and syncs title/body on save.
gh pr view <number> --json body -q .body
\n.development
Enforce tight Codex/Claude delivery loop with Bun-first testing, skill sync/reload, and commit quality gates.
tools
Manage environment variables and secrets with flow (always use Flow env store)
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------