How are you using claude-skills?

[Jeffallan]

Curious how people are integrating claude-skills into their workflows.

Tell us about your setup:

• What skills do you use most frequently?
• Are you using them for personal projects, work, or both?
• Any workflows or combinations that work particularly well together?
• What does your typical "skill-assisted" session look like?

Bonus questions:

• Has using skills changed how you approach problems?
• Any surprising wins or unexpected uses?
• What's still painful even with skills?

No wrong answers—whether you're using one skill occasionally or have built an entire workflow around them, we want to hear it.

Your responses help us understand real usage patterns and prioritize what to build next.

[boolean-maybe]

[EDIT] - apologies, I misunderstood the question, thought it's about Claude skills in general. But then it might serve as a skill request :) gitflow - a skill to checkout and name branches and create PRs to follow gitflow procedure

the skill I used most often is to control gitflow. We use gitflow in our development lifecycle + have some requirements about git commit message/github PR title and description. There are actually 2 skills:

dev PR

• run tests, linter, build, Docker (if present)
• use MCP to retrieve the ticket associated with the change
• present a numbered list of issues in progress. Let user enter a number to select from the list
• checkout new feature or fix branch (let AI assistant figure branch name from git diff)
• commit with appropriate message. Our format requires starting with the ticket number
• push new branch to remote
• create GitHub PR. Use appropriate formatting for PR title and description
• notify via slack that PR is waiting for review

release PR

• similar but must create release branch release/x.y.z
• first need to figure the next semver version depending on what language the project is in
• update version in code
• merge origin/master into release branch
• resolve conflict in version file in favor of release branch
• push new branch to remote
• create GitHub PR. Use appropriate formatting for PR title and description
• notify via slack that PR is waiting for review

enormously boring procedure if you do it manually like ten times a day