forge

KO | EN

gitlite — search

#javascript #hacktoberfest #ai #typescript #golang #go #linux #java #awesome #kubernetes #pytorch #mcp #openai #open-source

(★ 65)

A collection of agent skills for structured, GitHub-centric development.

파일 탐색기

최종 버전 다운로드 (.zip)

- architecture.md
- coding-guidelines.md
- development.md
- pr-workflow.md
- testing.md
- - barrel-imports.md
  - deep-modules.md
  - issue-operations.md
  - pattern-audit.md
  - phase-execution.md
  - plan-folder-spec.md
  - review-delegation.md
  - review-dimensions.md
  - review-rubric.md
  - vertical-slicing.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
.gitignore
AGENTS.md
CLAUDE.md
CONTEXT.md
README.md

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

<p align="center">
  <strong>Agent skills for structured development with pluggable issue tracking.</strong><br>
  One workflow. Seven skills. From idea to review-ready code.
</p>

<p align="center">
  <a href="CONTEXT.md">Context</a> &middot;
  <a href="docs/architecture.md">Architecture</a> &middot;
  <a href="docs/development.md">Development</a> &middot;
  <a href="docs/coding-guidelines.md">Guidelines</a> &middot;
  <a href="docs/testing.md">Testing</a> &middot;
  <a href="docs/pr-workflow.md">PR Workflow</a>
</p>

---

A forge is where raw material meets intention. You bring the codebase — these skills shape the workflow from issue to implementation to review.

---

## Skills

Forge skills follow the [Agent Skills](https://agentskills.io) open standard and work with any compatible agent.

| Skill | Command | Purpose |
|-------|---------|---------|
| Setup Project | `/forge-setup-project` | Set up or audit a project's context infrastructure for agentic engineering |
| Shape | `/forge-shape` | Shape a vague idea into a clear plan through one-at-a-time structured questioning |
| Create Issue | `/forge-create-issue` | Collaboratively plan and create Issues (GitHub, markdown, or other provider) |
| Implement | `/forge-implement <input>` | Implement from an Issue, plan file, or description |
| Reflect | `/forge-reflect` | Self-review changes (PR, branch, or uncommitted) |
| Address PR Feedback | `/forge-address-pr-feedback` | Address unresolved PR review comments |
| **Ship** | **`/forge-ship <input>`** | **Implement + review in one invocation** |

All skills accept optional trailing execution guidance using `-- <additional context>`.

## Workflow

The skills form a simple workflow — each step feeds into the next:

```
forge-setup-project → [forge-shape →] forge-create-issue → forge-implement → forge-reflect → forge-address-pr-feedback
                                                                        ╰──── forge-ship ────╯
```

`forge-ship` composes implement + review into a single invocation; its review always delegates to a fresh-context reviewer (the session authored the diff), adding a second pass only when risk justifies it. Standalone `forge-reflect` keeps tiny diffs inline when the session didn't author them. Scout and review work should use cheaper models when the runtime supports per-task model choice; otherwise they should inherit the parent session model cleanly.

## Install

Forge skills follow the [Agent Skills](https://agentskills.io) open standard and work with any compatible agent.

**Via [npx skills](https://skills.sh)** — auto-detects your agents and installs to all of them:

```bash
npx skills add mgratzer/forge
```

**Manual** — symlink into your agent's skills directory:

```bash
ln -s /path/to/forge/skills/forge-* /path/to/forge/skills/_shared <your-agent-skills-dir>/
```

Both `forge-*` skills and the `_shared/` directory are required — skills reference shared modules via `../_shared/` paths. Check your agent's docs for the correct skills directory path.

## Project Guidance

- [`AGENTS.md`](AGENTS.md) is the canonical project guidance file
- [`CLAUDE.md`](CLAUDE.md) is a compatibility symlink for tools that still look for that filename

## Documentation

| Document | Purpose |
|----------|---------|
| [Context](CONTEXT.md) | Shared vocabulary used across forge skills |
| [Architecture](docs/architecture.md) | Skill workflow, file format, design decisions |
| [Development](docs/development.md) | How to create and modify skills |
| [Coding Guidelines](docs/coding-guidelines.md) | Skill authoring conventions and style rules |
| [Testing](docs/testing.md) | How to validate skills manually |
| [PR Workflow](docs/pr-workflow.md) | Commits, PRs, branch naming, review process |

## Contributors

- [@denrase](https://github.com/denrase) — configurable git workflow idea ([#7](https://github.com/mgratzer/forge/pull/7))

## Contributing

1. Read [AGENTS.md](AGENTS.md) for project principles and conventions
2. Follow [docs/coding-guidelines.md](docs/coding-guidelines.md) for skill authoring rules
3. Test your changes by invoking the skill on a real project
4. Use conventional commits: `feat(skills): add new skill`

forge

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

forge

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README