Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

adept-contributing

Sterne7

Forks0

Aktualisiert17. Juni 2026 um 22:00

How to contribute to the adeptability (adept) Go CLI — build, the required pre-PR gates, conventional commits, and where things live. Apply when changing adept's own source, opening a PR, or adding a harness.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

itaywol

itaywol/adeptability

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	adept-contributing
description	How to contribute to the adeptability (adept) Go CLI — build, the required pre-PR gates, conventional commits, and where things live. Apply when changing adept's own source, opening a PR, or adding a harness.
allowed-tools	["Bash","Read","Edit"]

Contributing to adept

You are working on the adept CLI itself (Go 1.25, module github.com/itaywol/adeptability). Read AGENTS.md for architecture and invariants; this skill is the operational checklist.

Build & run

go build ./...
go build -o /tmp/adept ./cmd/adept && /tmp/adept --help

Gates you MUST pass before opening a PR (same as CI)

gofmt -l .            # must print nothing → fix with: gofmt -w .
go vet ./...
golangci-lint run     # config: .golangci.yml
go test -race ./...
go test -run E2E ./cmd/adept   # end-to-end against a freshly built binary

If any gate fails, fix it before pushing — CI runs the identical set on ubuntu/macos/windows.

Where things live

You're changing…	Go there
public types / interfaces / sentinel errors	`pkg/adept/` (types only — no behavior)
canonical field shape	`pkg/adept/` struct tags and `pkg/adeptschema/*.schema.json` together
a command	`internal/cli/commands_*.go`; wire deps in `internal/cli/deps.go`
a harness renderer	`internal/render/<id>/` + golden fixtures in its `testdata/`
sync / drift logic	`internal/harness/orchestrator.go`
3-way merge	`internal/merge/`
safety scanner	`internal/scan/`

Conventional commits (release-please reads these)

feat: → minor · fix:/perf: → patch · feat!:/BREAKING CHANGE: → major · refactor:/docs:/chore:/test:/ci: → no release. The squash-merge title becomes the changelog entry, so write it well.

Conventions

Wrap errors with context: fmt.Errorf("doing X: %w", err). Match with errors.Is against the sentinels in pkg/adept/errors.go — never on error strings. Add new sentinels there.
No package-level state, no init() side effects: dependencies flow through *Deps.
New behavior ships with tests; bug fixes ship with a regression test. Update golden fixtures in the same PR when output changes, and say why in the message.
Don't hand-edit CHANGELOG.md, .release-please-manifest.json, or version strings — release-please owns them.

Mehr aus diesem Repository

gleiches Repository

adept-self-improve

itaywol/adeptability

Capture a durable lesson, correction, or convention from this session as a reusable adept skill, then sync it to every harness. Apply when the user corrects you, when a fix generalizes, or when you say 'I'll remember that.'

2026-07-037

authoring-adept-agents

itaywol/adeptability

Write a good, portable adept agent (subagent): trigger-shaped description, one job per agent, generator/evaluator separation, explicit boundaries, restricted tools. Apply when creating or editing an agent file or running `adept agent add`.

2026-07-037

authoring-adept-loops

itaywol/adeptability

Compose a loop — a scheduled system that discovers work, hands it to agents, verifies with an independent evaluator, persists state, and reschedules itself. Apply when the user wants automation that runs on a timer, a triage/babysitter routine, or asks about `adept loop add`.

2026-07-037

authoring-adept-skills

itaywol/adeptability

Write a good, portable adept skill: pick the right activation, craft a triggering description, keep it scan-safe and within harness byte budgets. Apply when creating or editing a SKILL.md or running `adept skill add`.

2026-07-037

expertise-exchange

itaywol/adeptability

Team expertise billboard via `adept exchange`: ask teammates for expertise and stack responses. Apply when the user wants a colleague's input, mentions the exchange, or when you start using adept — sample open requests and offer to answer ones the user knows about.

2026-07-037

using-adept

itaywol/adeptability

Use the `adept` CLI to author AI skills once and render them into Claude Code, Cursor, Codex, Copilot, and OpenCode. Apply when installing/syncing skills, editing skill.yaml/SKILL.md, or touching .adeptability/.

2026-06-177

name	adept-contributing
description	How to contribute to the adeptability (adept) Go CLI — build, the required pre-PR gates, conventional commits, and where things live. Apply when changing adept's own source, opening a PR, or adding a harness.
allowed-tools	["Bash","Read","Edit"]

Contributing to adept

You are working on the adept CLI itself (Go 1.25, module github.com/itaywol/adeptability). Read AGENTS.md for architecture and invariants; this skill is the operational checklist.

Build & run

go build ./...
go build -o /tmp/adept ./cmd/adept && /tmp/adept --help

Gates you MUST pass before opening a PR (same as CI)

gofmt -l .            # must print nothing → fix with: gofmt -w .
go vet ./...
golangci-lint run     # config: .golangci.yml
go test -race ./...
go test -run E2E ./cmd/adept   # end-to-end against a freshly built binary

If any gate fails, fix it before pushing — CI runs the identical set on ubuntu/macos/windows.

Where things live

You're changing…	Go there
public types / interfaces / sentinel errors	`pkg/adept/` (types only — no behavior)
canonical field shape	`pkg/adept/` struct tags and `pkg/adeptschema/*.schema.json` together
a command	`internal/cli/commands_*.go`; wire deps in `internal/cli/deps.go`
a harness renderer	`internal/render/<id>/` + golden fixtures in its `testdata/`
sync / drift logic	`internal/harness/orchestrator.go`
3-way merge	`internal/merge/`
safety scanner	`internal/scan/`

Conventional commits (release-please reads these)

Conventions

Wrap errors with context: fmt.Errorf("doing X: %w", err). Match with errors.Is against the sentinels in pkg/adept/errors.go — never on error strings. Add new sentinels there.
No package-level state, no init() side effects: dependencies flow through *Deps.
New behavior ships with tests; bug fixes ship with a regression test. Update golden fixtures in the same PR when output changes, and say why in the message.
Don't hand-edit CHANGELOG.md, .release-please-manifest.json, or version strings — release-please owns them.