Create and submit a GitHub PR from the current branch
65
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Submit the current changes as a GitHub pull request.
Check the current state of the repository:
git status to see staged, unstaged, and untracked changesgit diff to see current changesgit log --oneline -10 to see recent commitsIf there are uncommitted changes relevant to the PR:
alice/, fix/, feat/)Push the branch and create the PR:
-u flag to set upstream trackinggh pr createAfter the PR is created:
/changelog <pr_number> to generate changelog files, then commit and push them/pr-description <pr_number> to update the PR descriptionReturn the PR URL to the user.
17205c1
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.