create-feedback-issue
SEMO 패키지 피드백 수집 및 이슈 생성 (Supabase DB 기반). Use when (1) /SEMO:feedback 명령어 호출, (2) 사용자가 SEMO 동작 오류 지적, (3) 개선 제안 요청.
Essential command-line tools and system utilities.
SEMO 패키지 피드백 수집 및 이슈 생성 (Supabase DB 기반). Use when (1) /SEMO:feedback 명령어 호출, (2) 사용자가 SEMO 동작 오류 지적, (3) 개선 제안 요청.
SOC II triage workflow for creating Linear tickets, branches, OpenSpec proposals, commits, and PRs. Use when asked to triage an issue, create a triage ticket, or start SOC II workflow.
Advanced Git operations using Git MCP. Manage branches, analyze commit history, review changes, handle merges, investigate file history, and automate Git workflows. Use when working with version control, code reviews, or Git debugging.
Master Jira integration using acli CLI, Jira REST API, issue management, sprint operations, JQL queries, and ADF comment formatting. Essential for Jira-based project management automation.
Creates PRDs with user stories for brownfield enhancements. Analyzes existing projects, defines requirements, and generates implementable user stories with acceptance criteria, tasks, and dev notes.
Implement features end-to-end in Laravel 12 + Inertia.js + React 19 + TypeScript. Use when building new features, wiring controllers to pages, or implementing CRUD operations. EXCLUSIVE to fullstack-developer agent.
Apply the Explore → Plan → Code → Commit workflow for tasks like implementing features, fixing bugs, refactors, or adding integrations. Use this when the user wants changes in a repo and wants higher reliability (read first, plan then commit/PR). Emphasize subagents for investigation during Explore, and use "think / think hard / think harder / ultrathink" during Plan when alternatives exist.
This skill should be used when the user wants to generate an implementation specification from triage output and clarifying questions. Trigger when user says "write spec", "create spec", "generate spec", or after completing a triage when the user wants to proceed to spec writing. The skill asks structured questions about decisions, then generates a detailed implementation spec with dependency graphs, migration details, and acceptance criteria.
Manage Jira Agile boards and sprints. Use when listing boards, creating sprints, or moving issues to/from sprints.
Synchronize AI swarms with GitHub Projects for visual task management and progress tracking. Use for project board automation, task synchronization, sprint management, and team coordination with GitHub Projects.
GitHub workflow conventions for Adynato projects. Covers creating PRs with gh CLI, writing thorough descriptions, and using stacked PRs for large deliverables. Use when creating pull requests, managing branches, or breaking down large features.
Enriches Jira tasks with comprehensive context, requirements analysis, and technical details through intelligent extraction, dependency mapping, and historical analysis
Use PROACTIVELY when creating releases after PR merges to main, or when user asks about versioning strategy. Automated git tagging agent that analyzes repository state, parses conventional commits, calculates semantic versions, and creates annotated git tags with GitHub releases. Supports monorepo namespaced tags with @ separator convention. Not for changelog generation or pre-release/alpha versioning.
Create smart commit linked to Jira issue. Use when the user wants to "commit", "smart commit", "jira commit", or "commit changes".
Fetch Semicolon team standards from docs wiki. Use when (1) providing workflow or process advice, (2) recommending DevOps strategies, (3) referencing team conventions for decision-making, (4) checking team standards compliance.
Guide for debugging issue on a specific code sections, pattern, or files. Used this skill when user asking for assistant when debugging an issues or explaining a code.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
This skill should be used when the user asks to "update repo description", "improve repository description", "generate topics", "add labels to repo", "optimize github metadata", "make repo more discoverable", "improve repo SEO", "update project description", or needs to create engaging repository descriptions and topics that improve discoverability. Analyzes project files to generate optimized GitHub metadata.
Team collaboration - remote, fetch, pull, push, clone, and team workflows
This skill should be used when working with Azure DevOps from the command line. Trigger when user mentions az devops, az repos, az pipelines, az boards, or asks about managing PRs, work items, pipelines, or repositories in Azure DevOps. Also trigger for questions about Azure DevOps CLI setup, authentication, or querying work items.
Multi-perspective project onboarding and sprint briefing. Simulates a cross-functional leadership team (PM, Designer, Architect, Engineer) ramping up on project status. Updates the Current Status section in PROJECT_STATE.md.
Manages GitHub issue parent-child relationships and sub-issues using REST and GraphQL APIs. Use when breaking down large work into Epics/Features/Tasks, creating work breakdown structures, converting markdown checklists to sub-issues, reordering sub-issues, or querying issue hierarchies. Handles ID confusion between REST numeric IDs and GraphQL node IDs.