feat: add help subcommand to /fullsend skill#6
Merged
Conversation
Context-aware onboarding companion that shows the agent pipeline, inspects the local .fullsend/ deployment, and links to upstream docs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a new /fullsend help [topic] subcommand to the Fullsend skill to provide developer-facing onboarding: explains the agent pipeline, inspects local .fullsend/ customizations, and links to upstream documentation.
Changes:
- Extended
/fullsendskill description and command/routing tables to include the newhelpsubcommand. - Added a new
references/help.mdreference implementing topic-based onboarding content and local deployment inspection guidance.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
.claude/skills/fullsend/SKILL.md |
Adds help [topic] to the command table and routes it to the new reference doc. |
.claude/skills/fullsend/references/help.md |
Introduces the help subcommand reference content (pipeline diagram, repo inspection steps, upstream links, topic routing). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+74
to
+76
| | **review** | `ready-for-review` label, `/fs-review` | Multi-dimension code review (correctness, security, style, docs) | | ||
| | **fix** | Review requests changes, `/fs-fix` | Addresses specific review findings, pushes fix commit | | ||
| | **retro** | PR merged/closed, `/fs-retro` | Retrospective on the full workflow — files improvement issues | |
Comment on lines
+18
to
+22
| ### 1. Resolve the target repo | ||
|
|
||
| Follow the repo resolution order from the SKILL.md `<repo_resolution>` section to find the repo with `.fullsend/` configuration. | ||
|
|
||
| If in a monorepo (e.g., `rhdh-plugins`), note this — the agent operates at repo level, not workspace level. |
| #### 4a. Read config.yaml | ||
|
|
||
| ```bash | ||
| cat <repo>/.fullsend/config.yaml |
Comment on lines
+100
to
+104
| ls <repo>/.fullsend/customized/harness/*.yaml 2>/dev/null | ||
| ls <repo>/.fullsend/customized/agents/*.md 2>/dev/null | ||
| ls <repo>/.fullsend/customized/skills/*/SKILL.md 2>/dev/null | ||
| ls <repo>/.fullsend/customized/env/*.env 2>/dev/null | ||
| ls <repo>/.fullsend/customized/policies/*.yaml 2>/dev/null |
Comment on lines
+159
to
+162
| ### 5. Upstream docs (topic: `setup` or all) | ||
|
|
||
| Present as a linked reference table. Construct URLs as `https://github.com/fullsend-ai/fullsend/blob/main/<path>`. | ||
|
|
Comment on lines
+149
to
+157
| #### 4e. Custom env files | ||
|
|
||
| For each `.env` in `customized/env/`, show what it sets: | ||
|
|
||
| ``` | ||
| ### Custom Env Files | ||
| - rhdh-toolchain.env — sets COREPACK_HOME=/tmp/corepack (writable dir for corepack) | ||
| - yarn-proxy.env — maps HTTP_PROXY → YARN_HTTP_PROXY (yarn ignores standard proxy vars) | ||
| ``` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/fullsend help [topic]subcommand — a context-aware onboarding companion for developers using fullsend agents.fullsend/directory to show what's customized (images, skills, env files, policies, prompt overrides)fullsend-ai/fullsend/docs/for deep dives — no content replicationagents,setup,customizationto show focused sectionsMotivation
The skill currently serves operators (validate, inspect, trigger, debug) but has no onboarding path for developers who want to use fullsend agents. Someone working in rhdh-plugins/boost needs to understand what agents exist, how they chain, and what's customized in their deployment.
Test plan
/fullsend help— should show pipeline diagram, local deployment summary, and upstream doc links/fullsend help agents— should show agent catalog section only/fullsendwith no args — should listhelpin the command table🤖 Generated with Claude Code