Skip to main content
在 Manus 中运行任何 Skill
一键导入
GitHub 仓库

agent-skills

agent-skills 收录了来自 comfuture 的 4 个 skills,并提供仓库级职业覆盖和站内 skill 详情页。

已收集 skills
4
Stars
4
更新
2026-07-24
Forks
0
职业覆盖
2 个职业分类 · 已分类 100%
仓库浏览

这个仓库中的 skills

gh-autoreview-resolve
软件开发工程师

Run a bounded GitHub automated-review and resolution loop for a specified pull request. Use when Codex must mark a PR ready for review, confirm the automated reviewer started through an eyes reaction, wait for a thumbs-up or concrete review response, validate and address review threads, request a narrowly focused `@codex review` follow-up when warranted, prevent review scope creep through PR comments or an issue-creator follow-up, and optionally merge with the user's preferred strategy.

2026-07-24
gh-implement-issue
软件开发工程师

Implement GitHub issues through a complete branch-to-PR workflow. Use when the user asks an agent to implement, fix, or ship a specific GitHub issue, including reading issue comments, confirming the implementation contract, creating a branch, making atomic commits, validating, pushing, opening or updating a PR, and handling issue-linked review/CI follow-up. Use related skills or integrations when available; otherwise inspect the repository, issue, PR, CI, and review context directly with the available tools.

2026-07-01
writing-strategy
技术写作员

Choose writing and narrative strategies from a curated bilingual strategy set, then produce a Markdown article outline or table of contents. Use when the user asks how to structure a draft, essay, article, post, proposal, column, case study, story, marketing copy, or other writing based on a topic, material, purpose, audience/readers, tone, or language. The skill selects a best-fit strategy, avoids overusing generic problem-solution frames, keeps Korean and English strategy names as canonical references, and displays strategy names in the user's output language unless bilingual names are explicitly requested.

2026-06-24
issue-creator
软件开发工程师

Create high-quality GitHub issues or issue drafts from repository evidence, user intent, and external documentation. Use when the user asks an agent to create, draft, file, open, or prepare an implementation issue, bug report, feature request, follow-up issue, or GitHub issue with researched facts, scope, non-goals, suggested direction, acceptance criteria, and validation notes.

2026-06-17