Add forge_workflow skill, retire forge_issues #14

Open
opened 2026-02-17 16:14:19 +00:00 by mik-tf · 0 comments
Member

Context

The issue→PR→merge workflow is the most repeated process across all Hero repos, but no skill documents it end-to-end. Currently forge_issues covers only API mechanics (curl calls), and PR creation has no skill at all. The writing style for issues and PRs (concise templates, WIP convention) is undocumented.

Goals

  • Add forge_workflow skill: complete issue→PR→merge flow with templates, style guide, WIP convention, and API calls inline
  • Retire forge_issues (its API content absorbed into forge_workflow, utility endpoints move to forge_api reference)
  • Update INDEX.md to reflect the change
## Context The issue→PR→merge workflow is the most repeated process across all Hero repos, but no skill documents it end-to-end. Currently `forge_issues` covers only API mechanics (curl calls), and PR creation has no skill at all. The writing style for issues and PRs (concise templates, WIP convention) is undocumented. ## Goals - Add `forge_workflow` skill: complete issue→PR→merge flow with templates, style guide, WIP convention, and API calls inline - Retire `forge_issues` (its API content absorbed into `forge_workflow`, utility endpoints move to `forge_api` reference) - Update INDEX.md to reflect the change
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
geomind_code/dev_docs#14
No description provided.