name	developer_pr_prep
display_name	Developer PR Prep
icon	account_tree
description	Prepare branches, diffs, tests, and GitHub PR text from Developer Studio.
enabled_by_default	false
version	1.0
tools	["developer"]
tags	["developer","github"]
author	Thoth

Developer PR Prep

Use this skill when the user wants to prepare, push, or open a pull request from Developer Studio.

Workflow:

Check workspace identity, branch, remote, dirty state, and GitHub CLI status.
Recommend a feature branch when the user is still on a protected or shared branch.
Review the diff and line counts.
Run the relevant tests or clearly state why they were not run.
Draft a PR title/body with summary, changed files, tests, and risk.
Treat push and PR creation as explicit user-approved actions.

If GitHub CLI is missing or unauthenticated, explain the shortest install/auth path for the current platform.

Más de este repositorio

mismo repositorio

Perform multi-source research on a topic and produce a structured report.

Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.

Guidance for querying and managing Thoth's own configuration and logs.

Capture unstructured thoughts and organize them into structured notes saved to memory.

Analyses datasets with professional rigour — statistical summaries, clear narratives, and well-chosen visualisations.

Structured workflow for creating professional designs — slide decks, documents, landing pages, app mockups, and motion storyboards.

name	developer_pr_prep
display_name	Developer PR Prep
icon	account_tree
description	Prepare branches, diffs, tests, and GitHub PR text from Developer Studio.
enabled_by_default	false
version	1.0
tools	["developer"]
tags	["developer","github"]
author	Thoth

Use this skill when the user wants to prepare, push, or open a pull request from Developer Studio.

Workflow:

Check workspace identity, branch, remote, dirty state, and GitHub CLI status.
Recommend a feature branch when the user is still on a protected or shared branch.
Review the diff and line counts.
Run the relevant tests or clearly state why they were not run.
Draft a PR title/body with summary, changed files, tests, and risk.
Treat push and PR creation as explicit user-approved actions.

If GitHub CLI is missing or unauthenticated, explain the shortest install/auth path for the current platform.