Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Proposal: move task-specific procedures out of AGENTS.md into `.claude/skills`

Open
  • Is something wrong?
#2,058 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
markdown
Domain
developer-experience, tooling

Research direction

Read the current AGENTS.md and compare it with the fork's approach in bompus/codegraph#241; the issue notes that the fork's version will not apply as-is. Identify which procedures belong in .claude/skills and which rules must remain in AGENTS.md, then check that the skills are discoverable by harnesses that do not load them. Done means the current repository's instructions are reorganized without carrying over fork-only rules.

Written by the indexing model from the issue text.

Description

AGENTS.md loads into every agent session. At 36 KB, most of it is procedure that only matters for one kind of task: cross-platform validation setup, the release flow, installer internals, changelog format. In the bompus/codegraph fork we moved those parts into repo skills and kept the root file for rules an agent can break without noticing. The root file went from 31,790 to 11,792 bytes (bompus/codegraph#241).

Each skill covers one kind of task:

  • codegraph-build-validation: build and test commands, test layout, cross-platform and Windows validation.
  • codegraph-retrieval: the evidence behind the retrieval rules, explore budgets, dynamic-dispatch channels, the Excalidraw worked example.
  • codegraph-installer: src/installer/ internals, agent targets, the Cursor --path quirk.
  • codegraph-release: changelog format and the release flow.
  • codegraph-issue-triage: checking a report against released, merged and in-progress state.

These stayed in the root file, since an agent that never opens the matching skill would break them silently:

  • A short retrieval block. Recoverable conditions return success-shaped guidance instead of isError, explore output never tells the agent to use Read, both explore budgets stay monotonic with file count, and partial dynamic-dispatch coverage is worse than none.
  • The Windows-gated test rule.
  • Installer changes need installer-targets tests and a changelog entry.
  • The README and docs sync rule.
  • A Skills section with one line per skill, telling the agent to read the matching SKILL.md before that work. Codex reads AGENTS.md but not .claude/skills, so this list is how skills reach harnesses that don't load them.

The fork's version won't apply here as-is. Some of its kept rules are fork-only (its branch and release policy, its Rust kernel build), and your AGENTS.md has changed since we split ours. If the idea fits, I can open a PR against the current file, or you can take the parts you want.

Dominant language
C
Stars
73.2k
Forks
4.7k
Avg merge
2h 13m
Merged PRs (30d)
418

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from colbymchenry/codegraph

All issues in colbymchenry/codegraph

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.