convez.ai
SkillAutomaçãoAvançado
jcl2018

Claude Skills Templates

jcl2018/claude-skills-templates

Pipeline doc-first para authoring de skills Claude com entrega dual (Code + Copilot)

Ver no GitHub
InicialPluginScore · de 0 a 100

Workbench de desenvolvimento orientado por documentação que entrega skills para Claude Code e bundles para GitHub Copilot a partir de uma única fonte de verdade. Inclui templates de itens de trabalho, workflows de validação, scripts de deploy e um sistema de registro de máquinas para governança de skills.

Instalação

$npx convez-ai jcl2018/claude-skills-templates

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 4 meses
Versão
v1.1.0
Issues abertas
1
Contribuidores
3

Casos de uso

  • Estruturar e validar trabalho em equipes técnicas com templates versionados
  • Executar workflows de verificação de saúde de skills e dependências
  • Escanear, catalogar e monitorar skills instaladas com análise de uso
  • Automatizar scaffold de work-items conformes e testes de QA com subagents
  • Manter skills sincronizados entre ambientes Claude e GitHub Copilot

Veredito

Projeto maduro e arquiteturalmente sólido para equipes que trabalham com multiple AI surfaces. O design doc-first, contracts de gateway e inteligência de deployment (Python CLI) o tornam referência para governança de skills em escala. Requer familiaridade com shell scripting, estrutura de work-items e filosofia de monorepo.

README

A tradução para o português deste README ainda está na fila.

claude-skills-templates

A doc-first development workbench: a work lifecycle pipeline, doc-contract enforcement, and authoring tooling. It ships from one source of truth to two delivery surfaces — Claude Code skills, and a self-contained GitHub Copilot bundle (work-copilot/) for machines without Claude. It is deliberately not Claude-skill-only.

Delivery surfaces

  • skills/ — Claude Code skills (the CJ_ workflow family + utilities), auto-discovered and listed below.
  • work-copilot/ — a self-contained GitHub Copilot bundle carrying the same work-item templates + /validate workflow to non-Claude machines. Deploy with python3 scripts/copilot-deploy.py install <target>; see work-copilot/README.md.

Repository layout

.
├── spec/               # machine registries (doc-spec / gate-spec / permission-policy / test-pipeline)
├── docs/                # human docs (philosophy.md, workflow.md, architecture.md) + generated views (doc-general.md, doc-custom.md, test-pipeline.md)
├── skills/              # Claude Code skills (the CJ_ family + utilities)
├── templates/           # work-item + doc authoring templates
├── work-copilot/        # the GitHub Copilot delivery bundle (Python-CLI deployed)
├── scripts/             # validate / test / deploy / helper scripts
├── work-items/          # the structured per-feature work tree (features, defects, tasks)
├── rules/               # skill-routing rules deployed to ~/.claude/rules/
├── CLAUDE.md            # agent operating instructions (auto-loaded by Claude Code)
├── CONTRIBUTING.md      # contributor authoring guide
├── CHANGELOG.md         # release history
└── TODOS.md             # operational backlog

For the full doc map (and the machine registry the validator parses), see spec/doc-spec.md.

Skills

NameDescriptionStatusPortabilityVersion
CJ_system-health~/.claude/ health dashboard with dependency graph and usage trends. Scans installed skills, builds dependency graph, checks filesystem health, surfaces skill usage analytics with behavioral topology overlay, invokes waza for config hygiene.activestandalone2.0.0
templatesSkill authoring template for new skills.activestandalone0.1.0
CJ_personal-workflowPersonal work item validation. Validates tracker files and work item directories against personal templates and personal-artifact-manifests.json. Templates + WORKFLOW.md are the single source of truth for structural rules.activeworkbench4.0.0
CJ_scaffold-work-itemScaffold a CJ_personal-workflow work item from an /office-hours design doc. Reads design + templates + manifest + WORKFLOW.md, produces a compliant work-item directory tree with all required artifacts. Runs /CJ_personal-workflow check at boundaries; idempotent (re-run on same input is NO-OP).experimentalstandalone1.0.1
CJ_qa-work-itemQA a CJ_personal-workflow work-item (user-story, defect, or task) per its test rows. For user-stories: runs Smoke Tests then dispatches a QA engineer subagent (fresh context, 5-min cap) for E2E verification per TEST-SPEC. For defects/tasks: runs test-plan rows as smoke-equivalent (no E2E subagent in v1). Writes findings to tracker journal; transitions Phase 2 qa-owned gates for user-stories; records [qa-pass] for defects/tasks. Idempotent (re-run on green work-item is NO-OP). Boundary check refuses on incomplete Phase 2.experimentalstandalone1.0.0
CJ_implement-from-specImplement a CJ_personal-workflow work-item (user-story, defect, task, or feature) from its input artifacts. Reads per-type input (SPEC+DESIGN for user-stories, RCA+test-plan for defects, TRACKER+test-plan for tasks; features delegate to a child user-story via AUQ), plans the change against the artifact's Components Affected / Data Flow, writes code via Read/Edit/Write tools. Sensitive-surface AUQ (catalog/manifest/validator). Propose-and-confirm by default; --auto for trivial changes (≤2 files, no sensitive surface). Idempotent (re-run on completed work-item is NO-OP). Boundary check refuses on incomplete Phase 1; verifies post-write compliance.experimentalstandalone1.0.0
CJ_suggestPrint a ranked top-5 of next-up work items from TODOS.md and tracker frontmatter. Internal phase-step skill rows (CJ_scaffold-work-item, CJ_implement-from-spec, CJ_qa-work-item, *-workflow validators) are filtered by default; pass --include-internal to surface them. Optional --for-skill / --limit flags pre-filter and extend the candidate window for downstream callers like /CJ_goal_todo_fix.experimentallocal-only1.2.0
CJ_goal_todo_fixAuto-resolve TODOs from TODOS.md into shipped PRs (formerly /CJ_goal; renamed v4.0.0; native drain mode added v4.2.0; --quiet added v4.3.0). Default mode (no args) drains up to 10 easy-fix TODOs end-to-end via the /CJ_implement-from-spec → /CJ_qa-work-item → /ship → /land-and-deploy chain — no /loop wrapper needed. Single-TODO mode preserved when arg is T-ID or fragment. --max-drain N caps the loop; --dry-run previews; --quiet suppresses Phase 3 summary AUQ for cron / /schedule consumers (autonomy ceiling preserved — /ship Gate #2 still fires per child). Workbench-only; halt-on-red preserved end-to-end.activelocal-only2.2.0
CJ_improve-queueWorkbench self-improvement skill. Three modes: (1) evaluate — fetch an Anthropic best-practices article, classify pattern fit against existing workbench skills via subagent reasoning, append a draft TODOS.md row if novel/conflict. (2) audit — offline repo self-scan for stale skills + missing frontmatter; emits draft rows directly. (3) research — orchestrator-driven WebSearch + per-result evaluate, with privacy gate. All rows land with markers; /CJ_suggest skips them until promoted. Workbench-only (macOS); domain allowlist + HTML-comment-wrap defense; mkdir-based write lock; atomic mv; backup rotation.experimentalstandalone0.2.0
CJ_goal_defectBug-description-to-shipped-fix orchestrator (the defect verb; experimental). Takes a plain bug description with NO pre-existing defect dir, scaffolds a throwaway .inbox/<slug>/DRAFT.md, root-causes it via /investigate as an Agent subagent (sentinel-wrapped JSON, Iron-Law: no root cause ⇒ HALT, nothing promoted or shipped), then on a populated root cause writes RCA + test-plan, promotes the draft to a canonical work-items/defects/uncategorized/D000NNN_<slug>/ dir (D-ID minted only after the Iron-Law gate passes), runs /CJ_qa-work-item (leaf subagent), and ships on the proven human-gated tail: /ship (Gate #2 always human) → /land-and-deploy --suppress-readiness-gate. Flat pipeline; depth ≤ 2 (no subagent-spawns-subagent). Consumes scripts/cj-goal-common.sh --mode defect for the deterministic worktree + pr-check phases. Halt taxonomy with next_action= / resume_cmd= / pr_url= journal entries; telemetry appends one JSONL line to ~/.gstack/analytics/CJ_goal_defect.jsonl. --dry-run previews the chain plan + write paths without mutation. Workbench-only (macOS). Drain mode / family-drain lock / --quiet all deferred. Use when: 'fix this bug end-to-end from a description', 'bug report to deployed fix', 'root-cause and ship a fix'.experimentallocal-only0.1.0
CJ_goal_featureOne-line-topic-to-reviewable-PR feature orchestrator (the feature verb; experimental). Takes a plain feature topic, creates a cj-feat-* worktree, runs /office-hours INLINE (the one interactive design phase; emits an APPROVED design doc — on not-APPROVED/abandoned it HALTs), then shows a design-summary approval gate in chat (a concise digest of the APPROVED doc + a single go/no-go before the autonomous build budget is spent — Abort HALTs as halted_at_design_gate and preserves the doc for resume), then SILENTLY (zero AUQ past the gate) dispatches /CJ_scaffold-work-item → /CJ_implement-from-spec → /CJ_qa-work-item as depth-≤2 leaf Agent subagents, and runs /ship INLINE with the diff-review AUQ suppressed to open a PR — then STOPs at the PR. The PR is the architecture gate (human review). No plan-review phase, no automatic merge, no /land-and-deploy (deploy is a separate human step). Strengthened resume: a state file records last_completed_phase + per-phase HEAD SHA + PR number and validates-before-skipping (recorded SHA must be ancestor-of/equal-to current HEAD AND any open PR must still be OPEN, else the affected phase restarts); office-hours resume re-locates the doc by the RECORDED PATH and re-confirms Status: APPROVED rather than a blind newest-glob; the design-summary gate re-fires on resume while still parked at the office-hours boundary and is skipped once the build has progressed. Consumes scripts/cj-goal-common.sh --mode feature for the deterministic worktree + pr-check phases; telemetry appends one JSONL line to ~/.gstack/analytics/CJ_goal_feature.jsonl. Halt taxonomy (green_pr_opened, halted_at_officehours/design_gate/scaffold/impl/qa/ship, already_shipped) with next_action= / resume_cmd= / pr_url= journal entries. --dry-run previews the chain plan without mutation. Workbench-only (macOS). An automatic merge-and-deploy path is unsafe-by-construction here (the handoff-gate denylist blocks exactly the skill surfaces every feature touches) and is parked, not deferred. Use when: 'build this feature end-to-end from a topic', 'one-line idea to a reviewable PR', 'scaffold + implement + qa from a topic and stop at the PR'.experimentallocal-only0.2.0
CJ_goal_taskSmall-ad-hoc-task-to-reviewable-PR orchestrator (the task verb; experimental). The lightweight sibling of /CJ_goal_feature: takes a plain free-text "<small task>" (refine a doc, add a file, clean up files, a one-line fix), runs a HARD complexity gate (refuses design-rework topics → routes to /CJ_goal_feature, refuses bug/investigation topics → routes to /CJ_goal_defect, refuses explicit-large-scope topics; HALTs as halted_at_too_complex), creates a cj-task-* worktree, then SILENTLY (zero AUQ) bash-scaffolds a type: task work-item (T-ID) directly from the topic via scripts/cj-task-scaffold.sh — NO /office-hours, NO design doc, NO pre-existing TODOS row — and dispatches /CJ_implement-from-spec → /CJ_qa-work-item as depth-≤2 leaf Agent subagents, folds doc updates via /CJ_document-release INLINE (Step 5.5 doc-sync; halt-on-red), runs a pre-ship portability gate (cj-goal-common.sh --phase portability-audit; halts [portability-red]), and runs /ship INLINE with the diff-review AUQ suppressed to open a PR — then STOPs at the PR. PR-stop only (like /CJ_goal_feature): no automatic merge, no /land-and-deploy; the PR is the review. Strengthened resume: a state file records last_completed_phase + per-phase HEAD SHA + work-item dir + PR number and validates-before-skipping; QA always re-runs on resume. Consumes scripts/cj-goal-common.sh --mode task for the deterministic worktree / sync / portability / pr-check / cleanup phases; telemetry appends one JSONL line to ~/.gstack/analytics/CJ_goal_task.jsonl. Halt taxonomy (green_pr_opened, halted_at_too_complex/not_isolated/scaffold/impl/qa/doc_sync/portability/ship, already_shipped) with next_action= / resume_cmd= / pr_url= journal entries. --dry-run previews the chain plan without mutation. Workbench-only (macOS). Use when: 'do this small task end-to-end', 'refine a doc / add a file / clean up files to a PR', 'fix this small thing and stop at the PR', 'a small ad-hoc cleanup that does not need design or investigation'.experimentallocal-only0.1.0
CJ_document-releaseWorkbench wrapper around upstream gstack /document-release (upstream skill, not in this catalog — invoked via Skill tool). Adds a --docs subset flag for per-invocation doc filtering (best-effort, documentation-only), a halt-on-red contract that emits [doc-sync-red] on upstream failure, and an auto-commit step gated by a doc-only whitelist DERIVED from the doc-spec.md registry (non-whitelist writes HALT with [doc-sync-non-doc-write]). Reads the registry at spec/doc-spec.md (resolved spec/-then-root; self-bootstraps it from the portable Common seed if missing; stub-scaffolds missing declared docs); a missing/invalid registry HALTs with [doc-sync-no-config] BEFORE any audit. Invoked inline by the 3 cj_goal orchestrators (CJ_goal_feature / CJ_goal_defect / CJ_goal_todo_fix) at Step 5.5 — between QA pass and /ship — so doc updates fold into the same code PR rather than chasing them post-merge.experimentallocal-only0.1.0
CJ_portability-auditStatic dependency lint for declared skill portability. Compares each catalog skill's declared portability field against its ACTUAL executed repo-local dependencies (root scripts/*.sh helpers, root config, CLAUDE.md, the manifest .source reach-back) using a strict tier ladder (standalone < local-only < workbench), an EXECUTED-vs-documented precision rule, bundled-own-script + scoped self-resolution-preamble carve-outs, and an optional portability_requires accepted-deps field. Emits a per-skill verdict (portable / portable-with-notes / findings:). Engine-in-script (scripts/cj-portability-audit.sh, resolved repo-local-first then via .source); also wired into validate.sh as an advisory check (exit 0 in v1; PORTABILITY_STRICT=1 flips to hard-fail). Workbench-only. Use when: 'audit skill portability', 'check declared-vs-actual dependencies', 'is this skill really standalone'.experimentalworkbench0.1.0

Quick Start

# Clone the repo
git clone https://github.com/jcl2018/claude-skills-templates.git
cd claude-skills-templates

# Validate the repo
./scripts/validate.sh

# Run full test suite
./scripts/test.sh

Getting started: the major workflows

Once the skills are installed (see Installation below), the workbench is driven by a handful of CJ_ front doors. Pick by what you have in hand:

You have...RunWhat it does
A one-line feature topic/CJ_goal_feature "<topic>"Designs, scaffolds, implements, QAs, and opens a reviewable PR — stops at the PR for human review.
A bug description/CJ_goal_defect "<bug>"Root-causes it, writes the fix + tests, and ships the deployed fix.
A TODOS.md backlog to drain/CJ_goal_todo_fixDrains shippable TODO rows into PRs (one, or up to N in drain mode).
"What should I work on?"/CJ_suggestPrints a ranked top-5 of next-up work items.
"Is my ~/.claude/ healthy?"/CJ_system-healthA read-only health dashboard for the install.

Every front door converges on the same /ship → /land-and-deploy tail. For the full workflow charts see docs/workflow.md; for the routing decision tree see docs/philosophy.md.

Installation

As a Claude Code plugin

claude plugin install claude-skills-templates@your-marketplace

Via git clone

git clone https://github.com/jcl2018/claude-skills-templates.git
claude --plugin-dir ./claude-skills-templates

Running on Windows

The workbench is POSIX-shell software. On Windows it runs two ways:

  • WSL2 (recommended). A real Linux environment — everything behaves exactly as on macOS/Linux, including symlink-based skills-deploy install.
  • Git Bash (supported). The bash that ships with Git for Windows — the same shell Claude Code uses to run skill preambles on Windows. Real symlinks are unavailable there, so skills-deploy install automatically falls back to copy-mode (real files + checksum-tracked drift detection) instead of symlinks.

Prerequisites (both paths): git, jq, gh, and python3 (the last only for the Copilot bundle / copilot-deploy.py). On Git Bash, git and jq come with Git for Windows; install gh from cli.github.com.

Line endings are pinned to LF by .gitattributes (* text=auto eol=lf), so shell scripts stay runnable under bash even when core.autocrlf is on. A windows-latest CI job (.github/workflows/windows.yml) runs the Windows-relevant test subset under Git Bash on every PR, so Windows support is exercised continuously. Run the same checks locally with bash scripts/windows-smoke.sh.

gstack plans live in this repo

Plans, designs, and reviews from gstack skills (/office-hours, /plan-ceo-review, /plan-eng-review, /context-save) land at <repo>/.gstack/ and are committed to git, so PR reviewers see the design intent that produced the code and design history travels alongside code history. Machine-local gstack state (sessions, analytics, learnings) stays out of git via .gitignore.

After cloning, wire up the per-machine redirect:

cd <repo>
./scripts/setup-gstack-symlink.sh

This creates a symlink from ~/.gstack/projects/<slug>/ (where gstack writes by default) to <main-repo>/.gstack/. Run from the repo root; the script resolves the main checkout via git rev-parse --git-common-dir so it works from worktrees too. Reverse with ./scripts/teardown-gstack-symlink.sh.

See CLAUDE.md for the .gstack/ (lateral/exploratory) vs work-items/ (structured per-feature) split convention.

Scripts

ScriptPurposeExit code
setup.shBootstrap: clone-or-update repo and deploy all skills1 on error
skills-deployInstall/remove/relink/doctor skills from this repo into ~/.claude/ (also deploys rules/*.md → ~/.claude/rules/)1 on error
validate.shCatalog-to-filesystem validation1 on error
test.shSmoke tests (superset of validate)1 on failure
test-deploy.shAutomated tests for skills-deploy in isolated temp dirs1 on failure
collection-version.shGet/bump/manifest for collection version1 on error
doctor.shSkill health diagnostics0 (advisory)
lint-skill.shContent-level skill linting0 (advisory)
deps.shDependency graph visualization0 (advisory)
generate-readme.shAuto-generate this README1 on write failure
sync-upstream.shCompare upstream gstack skills0 (local-only)
setup-hooks.shInstall pre-commit hook0
setup-gstack-symlink.shPer-machine: symlink ~/.gstack/projects/<slug>/ to <main-repo>/.gstack/ so gstack output commits in git. Idempotent; --force to re-point or merge non-empty target.1 on error
teardown-gstack-symlink.shReverse the gstack symlink: restore ~/.gstack/projects/<slug>/ to a real directory. Refuses if the symlink target doesn't match expected.1 on wrong target
copilot-deploy.pyInstall/doctor/remove the Copilot bundle in a target repo1 on error
skills-update-checkPassive update detector — emits SKILLS_UPGRADE_AVAILABLE banner when origin/main has a newer collection version. Auto-invoked from instrumented skill preambles.0 (advisory)

Contributing

See CONTRIBUTING.md for the full authoring guide.

Ver o original no GitHub

Bom para

Relacionados