Grey.ooo/agent-standards
Watch
2
0
Fork
You've already forked agent-standards
 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Add a skills/ layer, extracted from someones.computer #19

Merged
geusebio merged 1 commit from feature/someones-computer-skills into main 2026-08-13 12:43:08 +00:00
Conversation 0 Commits 1 Files changed 5 +1979 -1
geusebio commented 2026-08-13 12:39:10 +00:00
Owner
Copy link

Extracts four Forgejo-tracker skills from someones.computer's .claude/skills/ into a
new skills/ layer here, mirroring how commands/ already works: ask-me-questions,
issue-triage, resolve-pr-conflicts, triage-loop.

Genericized away from the source repo:

  • PHP/composer-specific gate commands → point at the consuming project's own quality-gate
    table (same pattern /vcs-check already uses)
  • someones.computer's specific milestone-wave names → kept the ordering principle, made
    the wave names illustrative
  • Docker-VM-specific capacity-calibration numbers (in triage-loop) → replaced with
    measure-your-own guidance

Unlike commands/, these skills aren't all-or-nothing — each assumes something beyond the
universal git+Forgejo+tea baseline (an active tracker, parallel-worktree capacity, a
quality-gate hookup). README adds a "Needs" table so a project picks only what fits, plus
the directory-symlink convention (.claude/skills/<name> → the skill's folder, not just
SKILL.md).

No code, no tests — docs/skill-definition files only.

Extracts four Forgejo-tracker skills from `someones.computer`'s `.claude/skills/` into a new `skills/` layer here, mirroring how `commands/` already works: `ask-me-questions`, `issue-triage`, `resolve-pr-conflicts`, `triage-loop`. Genericized away from the source repo: - PHP/composer-specific gate commands → point at the consuming project's own quality-gate table (same pattern `/vcs-check` already uses) - someones.computer's specific milestone-wave names → kept the ordering *principle*, made the wave names illustrative - Docker-VM-specific capacity-calibration numbers (in `triage-loop`) → replaced with measure-your-own guidance Unlike `commands/`, these skills aren't all-or-nothing — each assumes something beyond the universal git+Forgejo+`tea` baseline (an active tracker, parallel-worktree capacity, a quality-gate hookup). README adds a "Needs" table so a project picks only what fits, plus the directory-symlink convention (`.claude/skills/<name>` → the skill's folder, not just `SKILL.md`). No code, no tests — docs/skill-definition files only.
Four Forgejo-tracker skills (ask-me-questions, issue-triage,
resolve-pr-conflicts, triage-loop), genericized away from PHP/composer
specifics, someones.computer's milestone-wave taxonomy, and its hardware
capacity numbers. Mirrors how commands/ already works: symlink the ones
that fit into .claude/skills/, per project.

README documents a per-skill "Needs" table so a project adopts only what
matches its own setup, since skills (unlike commands) aren't all-or-nothing.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grey.ooo/agent-standards!19
No description provided.