solve-asana-issue
When you are asked to solve a issue with asana link given, consider this skill
When & Why to Use This Skill
This Claude skill automates the end-to-end lifecycle of software issue resolution by bridging project management and version control. It enables Claude to ingest Asana issue details, perform deep-dive root cause analysis across source code, implement technical fixes, and execute a standardized GitHub Pull Request workflow including automated testing and documentation.
Use Cases
- Automated Bug Fixing: Provide an Asana task link to have the agent automatically diagnose the bug, checkout a fix branch, and implement the necessary code changes.
- Seamless Project Management Integration: Maintain traceability by automatically linking GitHub Pull Requests back to original Asana issues with comprehensive technical summaries.
- Root Cause Investigation: Use the agent to explore complex codebases and documentation to identify the source of a reported issue, even if a code fix isn't immediately required.
- Standardized PR Generation: Ensure all bug fixes follow team best practices, such as targeting the develop branch, including test coverage, and providing structured advice for reviewers.
| name | solve-asana-issue |
|---|---|
| description | When you are asked to solve a issue with asana link given, consider this skill |
Following the instructions
- Read the Issue from asana and build up comprehensive understanding of the issue itself
- You can use any Skills, Tools, Command, Agent, or check any document include source code to figure out root cause of problem
- If you think it's no need to write code, report you conclusion to me
- If you think PR is need, you can carryout a Fix PR
Caveat: if carry out a Fix PR
- Make sure checkout from develop to your fix branch
- Make sure you write test cover fixed logic and test is passed
- Make PR is target to merge to develop
Caveat: if fire PR to Github
- Put Asana Issue link in front section if PR description
- Describe root cause and how to fix comprehensively, but not lengthly
- If PR is large, provide advice to reviewer