forgebee-help
Use when the user asks "what commands are available", "how do I use ForgeBee", "what can ForgeBee do", or needs a quick reference. Reads forgebee/INDEX.md as canonical source.
Best use case
forgebee-help is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when the user asks "what commands are available", "how do I use ForgeBee", "what can ForgeBee do", or needs a quick reference. Reads forgebee/INDEX.md as canonical source.
Teams using forgebee-help should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/forgebee-help/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How forgebee-help Compares
| Feature / Agent | forgebee-help | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when the user asks "what commands are available", "how do I use ForgeBee", "what can ForgeBee do", or needs a quick reference. Reads forgebee/INDEX.md as canonical source.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# ForgeBee Help — Quick Reference
## Objective
Answer "what commands / skills / agents does ForgeBee have, and which should I use right now?" Read the canonical source — `forgebee/INDEX.md` — and surface the relevant slice. Never hand-maintain a parallel command list (drift is the bug this skill exists to prevent).
## When this fires
- User asks "what commands are available"
- User asks "how do I use ForgeBee"
- User asks "what can ForgeBee do for X"
- User wants a quick reference / cheat sheet
- New project member onboarding to the framework
## Process
1. **Read `forgebee/INDEX.md`** — it's auto-generated by `scripts/build-index.js`, never hand-edited.
2. **If the user's question is generic** ("what commands?"): surface the **Quick Triage** section + the relevant category from Skills/Agents/Commands.
3. **If the user's question targets an intent** ("how do I add a feature?"): map the intent to a row in the Quick Triage table, and explain the recommended route in one paragraph.
4. **If a specific surface is named** ("what does /elicit do?"): quote the description from INDEX.md and link to the source file (`forgebee/commands/elicit.md`, etc.).
5. **For first-time users**: recommend running `/workflow` on a small task to feel the pipeline; ignore the other commands until needed.
## Never
- Never hand-maintain a parallel command list — read INDEX.md
- Never invent commands, skills, or agents not in INDEX.md
- Never recommend more than 2-3 commands at once — first-time overwhelm is the enemy
- Never confuse setup ("initialize ForgeBee on this project") with help ("how do I use ForgeBee") — that's the `forgebee-setup` skill's jobRelated Skills
forgebee-setup
Use when initializing ForgeBee on a new project — sets up CLAUDE.md, PM system, and project memory. For command-list questions, invoke the `forgebee-help` skill.
strategy-skeptic
Use when /growth reaches the strategy debate phase — argues AGAINST marketing strategy, finds weak positioning, audience gaps, flawed assumptions.
strategy-judge
Use when /growth strategy debate needs adjudication — rules on each item after reading blind Advocate and Skeptic cases. Approve, block, or flag.
strategy-advocate
Use when /growth reaches the strategy debate phase — argues FOR marketing strategy artifacts, defends quality, feasibility, and effectiveness in blind debate.
review-wordpress
Use when reviewing WordPress plugin or theme code for WP coding standards (WPCS), security (nonces, sanitization, escaping), hook naming, text domains, or plugin architecture.
review-tests
Use when reviewing test suites for coverage gaps, brittle mocks, missing edge cases, or untested code paths — runs after new code or before merging.
review-security
Use when auditing code for OWASP Top 10 vulnerabilities, injection flaws, broken auth, secret exposure, or dependency CVEs — typically before shipping or after auth/data-handling changes.
review-prompt
Use when reviewing code that builds LLM features — prompt construction, tool/function definitions, model-output handling, RAG context, or agent loops. Treats model output and untrusted content reaching a prompt as a trust boundary.
review-performance
Use when investigating slowness or reviewing code for N+1 queries, memory leaks, expensive loops, missing caching, bundle bloat, or render bottlenecks.
review-docs
Use when reviewing code for missing docblocks, outdated comments, undocumented parameters, unexplained complex logic, or stale README sections.
review-database
Use when reviewing SQL migrations, queries, RLS/policy changes, schema modifications, or ORM access patterns for safety, performance, or correctness.
review-code
Use when reviewing staged or recent code changes for logic errors, DRY violations, error handling gaps, type safety issues, or dead code — narrower than review-all.