Loading...
Loading...
Found 101 Skills
Linear project management via Composio API. Use when: (1) Listing, creating, or updating Linear issues (2) Getting teams, users, or workflow states (3) Managing projects or adding comments (4) Running custom GraphQL queries DO NOT use `linear` CLI - use Composio HTTP API only.
操作 CNB (cnb.cool) 平台上的 Issue。当用户需要创建、查询、更新 CNB 上的 Issue， 或需要管理 Issue 的标签、处理人、评论时，使用此 skill。 触发词: cnb issue、cnb 问题单、腾讯代码平台 issue、cnb.cool issue、cnb工单
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Linear GraphQL patterns for Symphony agents. Use `linear_graphql` for all operations — comments, state transitions, PR attachments, file uploads, and issue creation. Never use schema introspection.
Interact with GitHub issues - create, list, and view issues.
Github integration. Manage project management and ticketing data, records, and workflows. Use when the user wants to interact with Github data.
Full delivery pipeline: plan, build, ship, settle. Covers: shape/spec/design, TDD build, commit, PR creation, PR fix (CI/reviews/conflicts), PR polish, simplify, test coverage, verify ACs, walkthrough, issue management. Use when: shipping features, fixing PRs, creating PRs, building issues, simplifying code, checking quality, writing commits, managing issues. Trigger: /autopilot, /build, /shape, /commit, /issue, /check-quality, /test-coverage, /verify-ac, /pr-walkthrough.
Plan and file goals and feature issues through conversation. Use when the user wants to create goals, plan features, file issues, or discuss what to build next.
Use the GitHub CLI (gh) to perform core GitHub operations: auth status, repo create/clone/fork, issues, pull requests, releases, and basic repo management. Trigger for requests to use gh, manage GitHub repos, PRs, or issues from the CLI.
Create or update GitHub issues from screenshots, emails, messages, or any visual/text input. Extracts structured data, redacts PII, detects issue templates, proposes issues for approval, then files them via gh CLI. Don't use for GitLab/Jira tickets, opening pull requests, or fixing the bug described in the issue.
Create PLAN.md file with phase-based breakdown for issues. Use after creating an issue with /issue to break down work into phases.
Manage Jira issues, sprints, and epics using the jira CLI (ankitpokhrel/jira-cli). Use when asked to create, view, edit, list, move, assign, comment on, link, or delete Jira issues. Also use for sprint operations (list sprints, view current sprint, add issues to sprints) and epic operations (create epics, add/remove issues). Triggers on any Jira-related task, ticket management, sprint planning, or board workflow request.