chore: expose Claude Code skills for contributor access#321
Conversation
|
Size Change: 0 B 🆕 Total Size: 0 B |
kimyouknow
force-pushed
the
chore/expose-claude-skills
branch
2 times, most recently
from
44427dd to
85454ba
Compare
kimyouknow
force-pushed
the
chore/expose-claude-skills
branch
from
85454ba to
c074f5c
Compare
kimyouknow
force-pushed
the
chore/expose-claude-skills
branch
from
9833b75 to
12da4c2
Compare
Add .claude/skills/ and .claude/agents/ directories with guides for: - Commit, branch, and development workflow conventions - Code review, testing, and documentation standards - Monorepo setup, package publishing, and release management - Open source maintainer best practices Also includes: - CLAUDE.md with project-wide AI assistant instructions - Updated .gitignore for AI tool settings - Contributing guide improvements
kimyouknow
force-pushed
the
chore/expose-claude-skills
branch
from
12da4c2 to
2ba8874
Compare
Remove 5 skills that are not useful for contributors: - skill-initial-launch-checklist (one-time setup, already done) - skill-repository-standards (one-time setup, already done) - skill-monorepo-setup (maintainer-only infra decision) - skill-package-publishing (maintainer-only release flow) - skill-doc-writer (duplicates jsdoc-guide skill) Update agent-doc-writer to reference only jsdoc-guide skill.
|
|
||
| - Never commit sensitive files (.env, credentials) | ||
| - Push only when explicitly requested | ||
| - Never use --amend |
There was a problem hiding this comment.
why shouldn't we use amend?
There was a problem hiding this comment.
This is a safety rule for when the AI agent operates autonomously.
When a pre-commit hook fails, the commit is never actually created. If the agent then uses --amend, it would unintentionally modify the previous commit, potentially destroying someone else's work.
That said, the wording is a bit too strict — I'll soften it to "Never use --amend unless explicitly requested by the user."
| @@ -0,0 +1,400 @@ | |||
| # Open Source Maintainer Detailed Guide | |||
There was a problem hiding this comment.
is this skill for us?
There was a problem hiding this comment.
Good catch — this skill is primarily for maintainers, not contributors. I'll remove it from this PR and add it to .gitignore.
There was a problem hiding this comment.
what is this discord link for?
There was a problem hiding this comment.
It's the community Discord channel for questions and discussions! The description was missing — I'll add a brief explanation next to the link.
There was a problem hiding this comment.
why does project-decisions path in gitignore file?
There was a problem hiding this comment.
project-decisions/ is a skill that records project decision history. It contains internal references (Slack links, internal tool references) that shouldn't be exposed in a public repo, so it's gitignored.
This is also explained in the PR description under the "Excluded" section at the bottom!
- Soften --amend rule with explanation in agent-git-helper.md - Remove maintainer-only skill (skill-open-source-maintainer) and gitignore it - Add description to Discord link in CONTRIBUTING.md
Resolve conflicts in .github/CONTRIBUTING.md and .gitignore, keeping our branch's additions (Discord description, maintainer skill gitignore).
2 participants
Summary
[2/3] AI tool settings exposure series (based on #320)
Skills included (9 directories)
skill-scaffolderskill-test-writerskill-code-reviewerskill-jsdoc-guideskill-commitskill-branchskill-development-workflowskill-library-api-designskill-open-source-maintainerAgents included (4 files)
agent-code-revieweragent-doc-writeragent-git-helperagent-scaffolderRemoved skills (not useful for contributors)
skill-initial-launch-checklistskill-repository-standardsskill-monorepo-setupskill-package-publishingskill-doc-writerskill-jsdoc-guideExcluded:
project-decisions/(contains internal references, gitignored in PR 1)Test plan
project-decisions/remains git-ignored