‹ 首页

coding-process

@hawkyre · 收录于 昨天 · 上游提交 1 个月前

Entry point for all work. Identifies your task type and routes to the right workflow skill. Start here when beginning any task.

场景任务规划工作流启动效率工具

适合你，如果经常需要从零开始处理多种类型的任务，需要一个统一的入口。

/ 下载安装
https://github.com/hawkyre/hawk-skills/tree/main/skills/coding-process ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add hawkyre/hawk-skills/coding-process
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- hawkyre/hawk-skills/coding-process
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify hawkyre/hawk-skills/coding-process
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
28GitHub stars
~517上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 6ffb2d6 · 表述以原文为准
它做什么

Claude 会先判断你的编程任务类型（如小功能、大功能、修Bug、审查代码等），然后自动切换到对应的工作流程去处理。

什么时候触发

当你开始任何编程任务时，Claude 会先通过本技能识别任务类型并路由到合适的工作流。

装好后可以这样说
触发小功能流程
触发修Bug流程
触发代码审查流程
技能原文 SKILL.md作者撰写 · MIT · 6ffb2d6

Coding Process

This is the entry point for all work. It identifies the task type and routes to the appropriate workflow.

Process
  1. Load context:
  2. Read relevant standards from .agents/standards/ (check index.yml first)
  3. Read relevant common-mistakes from .agents/common-mistakes/ (check index.yml first)
  4. Check .plans/ for any existing plan files related to the current work
  1. Identify the task type from the user's description:

| Task Type | Route To | Trigger | |-----------|----------|---------| | Small feature / endpoint / component / config | /plan-small | Self-contained, fits in one PR | | Large feature / multi-system / architectural | /plan-large | Multi-day, multiple PRs, sequencing dependencies | | Delete feature / remove dead code / drop dependency | /remove-code | Removing capability | | Bug fix / error / crash / wrong behavior | /fix-bug | Something is broken | | Code review / audit / PR review | /code-audit | Reviewing code quality | | Aggressive cleanup of changes + tangibly-related code | /code-audit-hardcore | Same scope as code-audit, always-improve posture across related code (setup, wiring, siblings); big refactors route through plan skills | | Large PR review (30+ files) | /review-large-pr | PR too large for single audit | | Refactor / improve without behavior change | /refactor | Improving existing code | | Understand / explore / onboard | /learn-system | Building mental models |

  1. Route to the appropriate skill and follow its process.
Rules
  • Always load standards and common-mistakes before starting any workflow
  • If the task type is ambiguous, ask the user to clarify
  • review-plan (Workflow 8) and implement-plan (Workflow 9) are invoked directly when needed — they are not routed from here
  • If a plan file exists in .plans/, reference it and resume from where the last session left off
  • Big-output discipline. Heavy command output (project check, full git diff, repo-wide search, long log, large fetch) goes to /tmp/hawk-<skill>-<step>.log, then rg -n '<pattern>' /tmp/hawk-<skill>-<step>.log | head -50 extracts what you need. Read the file only with offset/limit. See README → Big-output discipline.
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…