Skip to content

docs(#608): migrate off .fullsend/customized/skills/ per ADR 0064 - #609

Merged
ralphbean merged 3 commits into
mainfrom
agent/608-migrate-off-customized-skills
Aug 13, 2026
Merged

docs(#608): migrate off .fullsend/customized/skills/ per ADR 0064#609
ralphbean merged 3 commits into
mainfrom
agent/608-migrate-off-customized-skills

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

Summary

  • Remove all references to the deprecated .fullsend/customized/skills/ overlay directory from AGENTS.md, docs/review.md, and docs/triage.md per ADR 0064.
  • Replace org-level skill override guidance with harness base: composition pattern (harness skills: entries with paths/URLs, composed via base:).
  • Add a concrete worked example in docs/triage.md showing how to override issue-labels via a custom triage harness with base: composition.

Changes

AGENTS.md § 7 (Skill resolution): Updated the resolution chain from three levels (repo → org overlay → platform) to two (repo → platform). Added a paragraph explaining how to override skills using harness base: composition, with a cross-reference to the existing worked example in docs/code.md.

docs/review.md: Replaced the customized/skills/ org-level override instruction with a reference to base: composition.

docs/triage.md: Same replacement as review.md, plus a new YAML example showing how to create a .fullsend/triage.yaml with base: pointing to the upstream harness and a local skills: entry.

Testing

  • Verified zero remaining customized/skills references via grep -r 'customized/skills'
  • Secret scan passed on all changed files
  • Gitlint passed on the commit message
  • Changes are docs-only — no runtime behavior affected

Closes #608

Post-script verification

  • Branch is not main/master (agent/608-migrate-off-customized-skills)
  • Secret scan passed (gitleaks — a0fec953cd3c8b877af9821551b503df88d394d8..HEAD)
  • PR body secret scan passed (gitleaks — no-git)
  • Pre-commit hooks passed (authoritative run on runner)
  • Tests ran inside sandbox

@fullsend-ai-coder
fullsend-ai-coder Bot requested a review from a team as a code owner July 31, 2026 18:09
@fullsend-ai-coder fullsend-ai-coder Bot added the ready-for-review Triggers review agent dispatch label Jul 31, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Jul 31, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 6:11 PM UTC · Completed 6:25 PM UTC
Commit: 52f65d5 · View workflow run →

@fullsend-ai-review

fullsend-ai-review Bot commented Jul 31, 2026

Copy link
Copy Markdown

Review

Findings

Medium

  • [protected-path] AGENTS.md — This PR modifies AGENTS.md, which is a protected governance file. The linked issue (docs: migrate off .fullsend/customized/skills/ per ADR 0064 #608) and PR description explain the rationale (migrating off deprecated .fullsend/customized/skills/ overlay per ADR 0064). Human approval is always required for protected-path changes, regardless of context.
Previous run

Review

Findings

Medium

  • [protected-path] AGENTS.md — This PR modifies AGENTS.md, which is a protected governance file. The linked issue (docs: migrate off .fullsend/customized/skills/ per ADR 0064 #608) and PR description explain the rationale (migrating off deprecated .fullsend/customized/skills/ overlay per ADR 0064). Human approval is always required for protected-path changes, regardless of context.

  • [incomplete-migration] FEATURES.md:37 — FEATURES.md still references the deprecated customized/skills/ overlay mechanism. While the line already marks the pattern as deprecated, the surrounding text still describes the old overlay as an option, which conflicts with the updated guidance in AGENTS.md, docs/review.md, and docs/triage.md.
    Remediation: Update FEATURES.md to remove the deprecated overlay description and describe only the base: composition pattern.

  • [stale-terminology] FEATURES.md:137 — FEATURES.md says "and to the agent frontmatter skills: array" but this PR updates terminology from "agent frontmatter" to "harness" in AGENTS.md, creating a terminology inconsistency.
    Remediation: Change "the agent frontmatter skills: array" to "the harness skills: array."

Previous run (2)

Review

Findings

Medium

  • [protected-path] AGENTS.md — This PR modifies AGENTS.md, which is a protected governance file. The linked issue (docs: migrate off .fullsend/customized/skills/ per ADR 0064 #608) and PR description explain the rationale (migrating off deprecated .fullsend/customized/skills/ overlay per ADR 0064). Human approval is always required for protected-path changes, regardless of context.

Low

  • [terminology-consistency] AGENTS.md:83 — Changed "Skills declared in agent frontmatter" to "Skills listed in harness". The verb change from "declared" to "listed" is a minor stylistic preference with no impact on clarity.

Labels: PR is a docs-only change updating AGENTS.md and docs/ files.

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review fullsend-ai-review Bot added requires-manual-review Review requires human judgment documentation Improvements or additions to documentation labels Jul 31, 2026
Comment thread docs/review.md Outdated

@ralphbean ralphbean left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this needs a couple changes before we can merge. See inline comments.

Comment thread AGENTS.md Outdated
Comment thread docs/review.md Outdated
Comment thread AGENTS.md
Comment thread docs/review.md Outdated
Comment thread docs/triage.md Outdated
@ralphbean

Copy link
Copy Markdown
Member

/fs-fix address the review findings

@fullsend-ai-coder

fullsend-ai-coder Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Finished Fix · ✅ Success · Started 6:52 PM UTC · Completed 6:58 PM UTC
Commit: 52f65d5 · View workflow run →

fullsend-ai-coder Bot added a commit that referenced this pull request Jul 31, 2026
- Remove stale "org level" / "org or repo level" terminology from
  AGENTS.md, docs/review.md, and docs/triage.md — the resolution chain
  now has only repo-level and platform-level, and the base: override is
  scoped to whichever repo holds the .fullsend/*.yaml file.
- Replace misleading cross-link to code.md#how-to-configure (which
  shows an image override, not a skills override) with inline YAML
  examples in AGENTS.md and docs/review.md, matching the pattern
  already used in docs/triage.md.
- Apply reviewer's suggested wording ("To override explicitly") in
  docs/review.md and docs/triage.md.

Addresses review feedback on #609
@fullsend-ai-coder

Copy link
Copy Markdown
Contributor Author

🔧 Fix agent — iteration 1 (human-triggered)

Addressed all 6 review findings (3 important, 2 moderate, 1 suggestion) by removing stale 'org level' terminology, replacing misleading code.md cross-links with inline skills-override YAML examples, and applying the reviewer's suggested wording.

Fixed (4):

  1. AGENTS.md: 'org or repo level' terminology inconsistent with new resolution chain (AGENTS.md): Removed 'at the org or repo level' qualifier — the override is repo-scoped via .fullsend/*.yaml, and the resolution chain now only has repo-level and platform-level.
  2. AGENTS.md: cross-link to code.md#how-to-configure points to image-override example, not skills (AGENTS.md): Replaced the generic 'for a worked example' cross-link with an inline YAML example showing base: composition with a skills: override (matching the pattern already in triage.md). Retained the cross-link narrowly for SHA/sha256sum values.
  3. docs/review.md: 'org level' terminology and misleading cross-link (docs/review.md): Applied reviewer's suggested wording ('To override explicitly'), removed the cross-link to code.md#how-to-configure, and added an inline YAML example with a narrower cross-link for SHA/sha256sum values.
  4. docs/triage.md: 'org level' terminology inconsistent with new resolution chain (docs/triage.md): Changed 'To override at the org level' to 'To override explicitly' for consistency with the other files and the new resolution chain.

Tests: passed

Next steps:

  • /fs-review — request a re-review of the changes
  • /fs-fix <your instruction> — run another fix pass with specific guidance
  • Push commits directly — review re-runs automatically on push
    Updated by fullsend fix agent

@ralphbean

Copy link
Copy Markdown
Member

/fs-fix rebase on main and resolve merge conflicts

@fullsend-ai-coder

fullsend-ai-coder Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Finished Fix · ✅ Success · Started 7:14 PM UTC · Completed 7:21 PM UTC

Commit: 266f4e5 · View workflow run →

Remove references to the deprecated org-level overlay directory
(.fullsend/customized/skills/) from AGENTS.md, docs/review.md, and
docs/triage.md. Replace with guidance to use harness base: composition
for skill overrides.

AGENTS.md § 7 now describes two-level resolution (repo-level and
platform-level) and points to harness base: composition for org-level
overrides. docs/review.md and docs/triage.md replace the customized/
overlay instructions with base: composition guidance, and docs/triage.md
adds a concrete worked example showing how to override issue-labels via
a custom triage harness.

Note: pre-commit could not run (network error fetching hooks in sandbox).
The post-script runs pre-commit authoritatively on the runner.

Closes #608
- Remove stale "org level" / "org or repo level" terminology from
  AGENTS.md, docs/review.md, and docs/triage.md — the resolution chain
  now has only repo-level and platform-level, and the base: override is
  scoped to whichever repo holds the .fullsend/*.yaml file.
- Replace misleading cross-link to code.md#how-to-configure (which
  shows an image override, not a skills override) with inline YAML
  examples in AGENTS.md and docs/review.md, matching the pattern
  already used in docs/triage.md.
- Apply reviewer's suggested wording ("To override explicitly") in
  docs/review.md and docs/triage.md.

Addresses review feedback on #609
@fullsend-ai-coder

Copy link
Copy Markdown
Contributor Author

🔧 Fix agent — iteration 2 (human-triggered)

Rebased agent/608-migrate-off-customized-skills onto latest origin/main. One conflict in docs/triage.md resolved: main had added new text referencing the deprecated customized/skills/ overlay (from PR #569), which this PR replaces with the base: composition pattern and a concrete YAML example. AGENTS.md and docs/review.md merged without conflicts. One pre-existing test failure (prerequisites-creates-allowed-issue) confirmed on origin/main — not introduced by this PR.

Fixed (1):

  1. rebase on main and resolve merge conflicts (docs/triage.md): Rebased branch onto origin/main (17 new commits). Resolved merge conflict in docs/triage.md by taking the PR version which replaces deprecated customized/skills/ references with base: composition guidance and a worked YAML example. AGENTS.md and docs/review.md auto-merged cleanly.

Tests: passed

Next steps:

  • /fs-review — request a re-review of the changes
  • /fs-fix <your instruction> — run another fix pass with specific guidance
  • Push commits directly — review re-runs automatically on push
    Updated by fullsend fix agent

@fullsend-ai-coder
fullsend-ai-coder Bot force-pushed the agent/608-migrate-off-customized-skills branch from 266f4e5 to d4763f8 Compare August 10, 2026 19:21
@fullsend-ai-review

fullsend-ai-review Bot commented Aug 10, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 7:22 PM UTC · Completed 7:38 PM UTC

Commit: d4763f8 · View workflow run →

@ralphbean

Copy link
Copy Markdown
Member

/fs-fix

@fullsend-ai-coder

fullsend-ai-coder Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Finished Fix · ✅ Success · Started 9:03 PM UTC · Completed 9:09 PM UTC

Commit: d4763f8 · View workflow run →

Remove deprecated customized/skills/ overlay reference from the Skill
override table entry and update "agent frontmatter" terminology to
"harness" for consistency with the rest of the PR.

Addresses review feedback on #609
@fullsend-ai-coder

Copy link
Copy Markdown
Contributor Author

🔧 Fix agent — iteration 2 (human-triggered)

Addressed 2 of 3 review findings by updating FEATURES.md: removed deprecated customized/skills/ overlay reference and updated 'agent frontmatter' terminology to 'harness'. Disagreed with 1 finding (protected-path is informational, requires human approval).

Fixed (2):

  1. [incomplete-migration] FEATURES.md:37 still references deprecated customized/skills/ overlay (FEATURES.md): Removed the sentence 'The older customized/skills/ overlay in the org .fullsend config repo is deprecated by ADR 0064.' from the Skill override table entry. The surrounding text already describes only the base: composition pattern, so removing this sentence completes the migration.
  2. [stale-terminology] FEATURES.md:137 uses 'agent frontmatter' instead of 'harness' (FEATURES.md): Changed 'add it to harness/.yaml under skills: and to the agent frontmatter skills: array' to 'add it to the harness skills: array in harness/.yaml' — updating the terminology to 'harness' for consistency with the rest of the PR and removing the resulting redundancy.

Disagreed (1):

  1. [protected-path] AGENTS.md requires human approval: Informational finding only — AGENTS.md modification requires human approval, which is not an actionable code change for the fix agent. The human reviewer must approve protected-path changes directly.

Tests: passed

Next steps:

  • /fs-review — request a re-review of the changes
  • /fs-fix <your instruction> — run another fix pass with specific guidance
  • Push commits directly — review re-runs automatically on push
    Updated by fullsend fix agent

@fullsend-ai-review

fullsend-ai-review Bot commented Aug 12, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 9:10 PM UTC · Completed 9:22 PM UTC

Commit: 55c278e · View workflow run →

@ralphbean ralphbean left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked the AGENTS.md diff and the docs/code.md#how-to-configure link the new examples point to — anchor's real, and it walks through getting the SHA/sha256sum values. Looks good at 55c278e.

@ralphbean
ralphbean added this pull request to the merge queue Aug 13, 2026
Merged via the queue into main with commit 8989607 Aug 13, 2026
13 checks passed
@ralphbean
ralphbean deleted the agent/608-migrate-off-customized-skills branch August 13, 2026 18:16
@fullsend-ai-retro

fullsend-ai-retro Bot commented Aug 13, 2026

Copy link
Copy Markdown

🤖 Finished Retro · ✅ Success · Started 6:19 PM UTC · Completed 6:41 PM UTC

Commit: 55c278e · View workflow run →

@fullsend-ai-retro

Copy link
Copy Markdown

Retro: PR #609 — migrate off .fullsend/customized/skills/ per ADR 0064

Timeline

When What
Jul 31 17:55 Issue #608 opened by ralphbean
Jul 31 17:57 Triage completed (run), rated Medium severity
Jul 31 18:01 Code agent dispatched (run)
Jul 31 18:09 PR #609 created — changed AGENTS.md, docs/review.md, docs/triage.md
Jul 31 18:25 Review agent (run) found 1 medium (protected-path) + 1 low (terminology verb). Missed substantive issues.
Jul 31 18:50 ralphbean requested changes: 3 important (stale "org level" terminology) + 2 moderate (cross-link to wrong example)
Jul 31 18:58 Fix iteration 1 (run) addressed all 6 human findings
Aug 10 19:21 Fix iteration 2 (run) rebased onto main, resolved merge conflict
Aug 10 19:38 Review re-run (run) found 2 new FEATURES.md findings
Aug 12 21:09 Fix iteration 3 (run) fixed FEATURES.md
Aug 12 21:22 Review (run) — only protected-path remains
Aug 13 17:56 Human approval; merged

What went well

  • Triage and code agents performed well. Issue triaged and PR created within 15 minutes.
  • Fix agent was effective across all 3 iterations. Correctly handled human review feedback, merge conflict resolution, and review agent findings.
  • Review agent improved across iterations. The second review pass (Aug 10) found FEATURES.md issues the first pass missed.

Key gaps

  • Review agent initial pass missed all substantive issues. The human reviewer found 5 actionable findings — 3 important ("org level" terminology inconsistent with the new 2-level resolution chain across AGENTS.md, docs/review.md, docs/triage.md) and 2 moderate (cross-link to code.md#how-to-configure shows image overrides, not skills overrides). All were within the changed files; no extra exploration was needed.
  • Code agent's grep verification was inaccurate. The PR description claimed "Verified zero remaining customized/skills references via grep -r 'customized/skills'" but FEATURES.md:37 still contained the string. The review agent did not independently verify this claim.

Existing issue evidence

  • #720 (correctness sub-agent should verify framing statements match content): This PR provides supporting evidence — the new text used "org level" terminology while the PR itself was eliminating org-level resolution.
  • #427 (autonomy evidence for docs-only PRs): This PR provides counter-evidence — the review agent missed substantive issues on a docs-only PR. The human review was essential for correctness on this migration task.

Proposals filed

ggallen pushed a commit that referenced this pull request Aug 19, 2026
- Remove stale "org level" / "org or repo level" terminology from
  AGENTS.md, docs/review.md, and docs/triage.md — the resolution chain
  now has only repo-level and platform-level, and the base: override is
  scoped to whichever repo holds the .fullsend/*.yaml file.
- Replace misleading cross-link to code.md#how-to-configure (which
  shows an image override, not a skills override) with inline YAML
  examples in AGENTS.md and docs/review.md, matching the pattern
  already used in docs/triage.md.
- Apply reviewer's suggested wording ("To override explicitly") in
  docs/review.md and docs/triage.md.

Addresses review feedback on #609
ggallen pushed a commit that referenced this pull request Aug 19, 2026
Remove deprecated customized/skills/ overlay reference from the Skill
override table entry and update "agent frontmatter" terminology to
"harness" for consistency with the rest of the PR.

Addresses review feedback on #609
ggallen pushed a commit to ggallen/agents that referenced this pull request Aug 19, 2026
- Remove stale "org level" / "org or repo level" terminology from
  AGENTS.md, docs/review.md, and docs/triage.md — the resolution chain
  now has only repo-level and platform-level, and the base: override is
  scoped to whichever repo holds the .fullsend/*.yaml file.
- Replace misleading cross-link to code.md#how-to-configure (which
  shows an image override, not a skills override) with inline YAML
  examples in AGENTS.md and docs/review.md, matching the pattern
  already used in docs/triage.md.
- Apply reviewer's suggested wording ("To override explicitly") in
  docs/review.md and docs/triage.md.

Addresses review feedback on fullsend-ai#609
ggallen pushed a commit to ggallen/agents that referenced this pull request Aug 19, 2026
Remove deprecated customized/skills/ overlay reference from the Skill
override table entry and update "agent frontmatter" terminology to
"harness" for consistency with the rest of the PR.

Addresses review feedback on fullsend-ai#609
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation ready-for-review Triggers review agent dispatch requires-manual-review Review requires human judgment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: migrate off .fullsend/customized/skills/ per ADR 0064

1 participant