Skip to content

Add markdown file documenting how to use fullsend with this repository #6

Description

@johnmcollier

Add markdown file documenting how to use fullsend with this repository

Activity

  1. fullsend-ai-triage commented on Sep 1, 2026

    @fullsend-ai-triage

    🤖 Finished Triage · ✅ Success · Started 2:53 PM UTC · Completed 2:57 PM UTC

    Commit: e416f23 · View workflow run →

    Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $0.74

  2. fullsend-ai-triage commented on Sep 1, 2026

    @fullsend-ai-triage

    This follows the same pattern as issue #2 (adding CONTRIBUTING.md). The repo's .fullsend/config.yaml enables six roles — triage, coder, review, fix, retro, and prioritize — so the new doc should cover what each role does and how contributors interact with them.

    Proposed test case

    # Verify the doc exists and references all configured roles
    for role in triage coder review fix retro prioritize; do
      grep -qi "$role" FULLSEND.md || echo "Missing: $role"
    done

    Next steps:

    • /fs-code — agent creates a PR to implement this issue
    • /fs-code <your instruction> — agent implements with your specific guidance
  3. fullsend-ai-coder commented on Sep 1, 2026

    @fullsend-ai-coder
    Contributor

    🤖 Finished Code · ✅ Success · Started 2:58 PM UTC · Completed 3:02 PM UTC

    Commit: e416f23 · View workflow run →

    Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $1.14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions