lidr-academy/develop-backend
ai-specs/skills/develop-backend/SKILL.md
Implement backend Jira tickets end-to-end with tests, documentation updates, and PR creation.
$ install --global
skillsauthnpx skillsauth add lidr-academy/ai4devs-lti-extended develop-backendInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 6:46 AM126.4s1 file scanned
SKILL.md
- name:
- develop-backend
- description:
- Implement backend Jira tickets end-to-end with tests, documentation updates, and PR creation.
- author:
- LIDR.co
- version:
- 1.0.0
develop-backend Skill
Use it when this workflow is required in the project.
Instructions
Please analyze and fix the Jira ticket: $ARGUMENTS.
Follow these steps:
- Understand the problem described in the ticket
- Search the codebase for relevant files
- Start a new branch using the ID of the ticket (for example SCRUM-1)
- Implement the necessary changes to solve the ticket, following the order of the different tasks and making sure you accomplish all of them in order, like writing and running tests to verify the solution, updating documentation, etc.
- Ensure code passes linting and type checking
- Stage only the files affected by the ticket, and leave any other file changed out of the commit. Create a descriptive commit message
- Push and create a PR, using the ID of the ticket (for example SCRUM-1) so it gets linked in Jira ticket
Remember to use the GitHub CLI (gh) for all GitHub-related tasks.
Related Skills
lidr-academy/show-spec-working
tools
VerifiedTrustedCommunity
Use when the user asks "show me X", "demo X", "walk me through X", "how X works" or requests a live feature demonstration from a spec, feature or ticket.
123SKILL.mdUpdated May 10, 2026
lidr-academy/adversarial-review
development
VerifiedTrustedCommunity
Use when the user requests an adversarial review, red-team review, devil's advocate check, or independent verification pass before archiving an OpenSpec change.
123SKILL.mdUpdated May 10, 2026
lidr-academy/writing-skills
testing
VerifiedTrustedCommunity
Use when creating new skills, editing existing skills, or verifying skills work before deployment
123SKILL.mdUpdated May 9, 2026
lidr-academy/using-git-worktrees
tools
VerifiedTrustedCommunity
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
123SKILL.mdUpdated May 9, 2026