Skip to content

docs(#6232): add skill doc-integration checklist to AGENTS.md - #6235

Open
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/6232-agents-skill-doc-checklist
Open

docs(#6232): add skill doc-integration checklist to AGENTS.md#6235
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/6232-agents-skill-doc-checklist

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

Summary

Add a doc-integration checklist rule to AGENTS.md so that contributors adding new skills under skills/ check the user-facing guides for cross-reference opportunities.

Related Issue

Closes #6232

Changes

  • Added a new bullet to the "How to work in this repo" section of AGENTS.md, placed after the existing documentation guidance rules (vitepress sidebar config and stale-reference grep)
  • The rule names three specific guide files to check: docs/guides/user/customizing-with-skills.md, docs/guides/user/bring-your-own-agent.md, and docs/guides/README.md
  • Uses advisory phrasing ("check for opportunities") rather than a hard requirement, avoiding unnecessary boilerplate when a skill doesn't warrant user-guide integration

Testing

  • make lint — docs-only change, no Go or test code modified
  • Secret scan passed
  • gitlint passed
  • All three referenced guide files verified to exist

Checklist

  • PR title follows Conventional Commits (correct type, ! for breaking changes)
  • No DCO sign-off (autonomous agent commit)

Closes #6232

Post-script verification

  • Branch is not main/master (agent/6232-agents-skill-doc-checklist)
  • Secret scan passed (gitleaks — 4bfc8988be00438547d53e2d4ab1fa4211563eaa..HEAD)
  • PR body secret scan passed (gitleaks — no-git)

Add a rule to the "How to work in this repo" section instructing
contributors to check user-facing guides for cross-reference
opportunities when adding a new skill under skills/. The rule
names the three most relevant guide files (customizing-with-skills,
bring-your-own-agent, guides README) and uses advisory phrasing
("check for opportunities") to avoid unnecessary boilerplate when
a skill does not warrant user-guide integration.

Motivated by PR #6202, where the initial commit created a skill
file without updating any existing documentation, requiring a
human rewrite to add cross-references in three guide files.

Closes #6232
@fullsend-ai-coder
fullsend-ai-coder Bot requested a review from a team as a code owner August 14, 2026 16:59
@fullsend-ai-coder fullsend-ai-coder Bot added the ready-for-review Agent PR ready for human review label Aug 14, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Aug 14, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 5:00 PM UTC · Completed 5:10 PM UTC

Commit: f1e670e · View workflow run →

@fullsend-ai-review

Copy link
Copy Markdown

Review

Findings

Medium


Labels: PR modifies AGENTS.md (governance file) with a rule about skills/ directory doc integration

@fullsend-ai-review fullsend-ai-review Bot added requires-manual-review Review requires human judgment component/docs User-facing documentation component/skills labels Aug 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component/docs User-facing documentation component/skills ready-for-review Agent PR ready for human review requires-manual-review Review requires human judgment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AGENTS.md: add doc-integration checklist for new skills

0 participants