fsd:create-issue-and-commit

To automate creating a Linear issue and opening a GitHub pull request, you can use a workflow automation Skill that parses your code changes, creates the issue, commits to a managed branch, and opens the linked PR.

Yes, you can generate a conventional commit message and branch name from your git diff by running a Skill that infers the issue description from your staged changes and applies a specific naming convention.

The best way to link a Linear issue to a new GitHub pull request automatically is to use a code shipping workflow tool that creates the issue first, then embeds the issue reference into the PR body during creation.

Yes, you need both Linear and GitHub repository access to automate branch management and issue creation, as the workflow utilizes the Linear API for issue tracking and the GitHub API for branch and PR management.

Automating issue creation and PR opening streamlines the code shipping workflow by creating a complete paper trail in one action, eliminating manual data entry across separate platforms for on-the-fly work.

You should avoid automating the commit and pull request workflow if your project lacks a standard git repository setup or does not use Linear and GitHub, as the automation requires these specific platform integrations.