skills/create-pr/SKILL.md
Push the current branch and create a Pull Request for ByteSync. Use when the user wants the agent to push a branch and open a PR, and requires the PR title and description in English.
npx skillsauth add pow-software/bytesync create-prInstall 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.
Provide a short workflow to push the current branch and open a Pull Request with an English title and description using the gh CLI.
Confirm the current branch name and whether there are uncommitted changes. If changes remain, ask whether to commit before pushing.
Push the current branch to the remote. If the user did not specify a tool, default to using the gh CLI context and run a normal git push for the current branch.
Example:
git push -u origin HEAD
Create a Pull Request using gh pr create with:
Provide a minimal PR template to pass to gh pr create:
Title: [type] Short summary
Description:
Ensure the template is in English and matches the repo's PR format when applicable.
Keep the response focused on the push + PR actions, avoiding extra steps unless the user asks.
development
Execute an implementation plan end-to-end in the ByteSync repo. Use when the user asks to implement a previously established plan step by step, requires creating a branch before coding, expects regular commits during progress, and wants build/test validation.
development
Produce a structured implementation plan (no code) from an existing specification or deep analysis. Use after a spec is written to outline steps, file touch points, sequencing, and test strategy without writing code.
development
Analyze a GitHub issue in depth and produce a detailed specification based on codebase analysis. Use when given a GitHub issue URL or number and asked to deeply analyze requirements, scan the repository, and write a structured spec (no code changes).
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.