claude

nolte-shared

Shared Claude Code skills and agents for consistent development workflows across projects.

0 on GitHubby noltev0.1.11MITupdated 3 days ago
/

Plugin nolte-shared from marketplace nolte-shared in nolte/claude-shared. Commands read from the repo's manifest — 2 days ago.

What it installs

Skills (36)

  • audience-identify

    Runs the audience-identification methodology from spec/project/audience-identification/ against a bounded context (software module, service, library, or whole project) and produces an authoritative audience artifact. Invoke when the user says things like "identify audiences for this module", "who ar

  • backlog-delivery-orchestrate

    Drives the open issue backlog to merged pull requests on `develop` in one run: partitions it first (`issue-backlog-partition`), runs the resulting lanes with at most three in parallel through `issue-batch-orchestrate` and `issue-orchestrate` (which dispatch the expert skills and agents) up to a loca

  • backstage-catalog-generate

    Generates a schema-valid Backstage catalog-info.yaml from an existing software project, conforming to spec/project/backstage-catalog-generation/. Inspects the repo (language/structure, remote slug, CODEOWNERS, OpenAPI/AsyncAPI/GraphQL/gRPC specs, colocated docs), infers the per-kind MUST-floor field

  • blog-author-trigger

    Operationalises spec/project/blog-author-trigger/: on a feature→done transition it derives a blog-post briefing from the feature record, computes a new/update/defer suggestion from the blog consumer's existing-post index, presents the three-way operator choice, and either dispatches blog-author with

  • blog-author

    Drafts a bilingual EN-canonical + DE-translated blog-post pair per this plugin's blog-author, post-writing-style, and post-audience-communication specs. Walks the operator through briefing inputs (topic-as-thesis, grounded artefact, primary audience, source list, slug, cross-language binding key), w

  • cicd-pipeline-design

    Designs, scaffolds, and audits a repository's CI/CD pipeline against spec/project/continuous-integration/ (pre-merge stage sequence, reproducible inputs, cache discipline, local↔CI parity), spec/project/continuous-delivery/ (artifact immutability, provenance, the artifact-to-securing-stage matrix, r

  • continuous-improvement-triage

    Operationalises spec/project/continuous-improvement/ by triaging portfolio audit findings, classifying them against the available specialist catalog, and dispatching hands-on remediation to the most specialised available Claude agent or skill. Invoke when the user asks to \"triage continuous-improve

  • cookiecutter-template-manage

    Manages the lifecycle of a Cookiecutter template: scaffolds a new template or refactors an existing one (with mid-flow user confirmation of variable names and choice defaults), hardens Cookiecutter hooks, and sets up a pytest-cookies test harness. Invoke when the user says "manage a Cookiecutter tem

  • docs-audience-tracks-apply

    Audits a repository against the canonical-language file under spec/project/docs-audience-tracks/ and, with per-item user approval, scaffolds or patches the documentation-tracks layer: per-page `track:` frontmatter across the per-language docs/ tree, required user-docs and developer-docs content bloc

  • docs-dry-refactor

    Operationalises spec/project/mkdocs-structure/ §Snippet inclusion (DRY). Detects paragraph duplication across MkDocs pages and, with per-snippet user approval, extracts duplicates into `mkdocs-include-markdown-plugin` includes pointing at a canonical source (preferring a live source file over a dedi

  • github-issue-templates-apply

    Applies the canonical-language file under spec/project/github-issue-templates/ to a target repository — detect the project type, resolve or dispatch the audience artefact, derive triage questions, and scaffold or update .github/ISSUE_TEMPLATE/ (bug_report.yml, feature_request.yml, config.yml, plus p

  • issue-backlog-partition

    Surveys the complete open issue backlog of one repository and partitions it per `spec/project/issue-batch-integration/` §J: pre-establishes each issue's class, bounded verdict, asserted cause, and touch surface in an isolated context, forms groups only on the three admission predicates (thematic cou

  • issue-batch-orchestrate

    Orchestrates a cluster of related GitHub issues as one group per `spec/project/issue-batch-integration/`: admits members on thematic coupling, shared touch surface, or dependency chain, analyses the group across its members for a structural cause, writes a group pre-analysis carrying a completeness

  • issue-orchestrate

    Orchestrates a raw GitHub issue to an open, audit-trailed pull request per `spec/project/issue-orchestration/`. Comprehends the issue (body, comments, labels, linked items, repo surface), classifies it (`bug / feature-request / spec-change / security / docs / refactor / question / infra`), decompose

  • lektorat-apply

    Reviews existing Markdown prose against six editorial dimensions (readability, comprehensibility, grammar, style, audience-fit, idiomatic naturalness) defined in `spec/project/lektorat/`. Three operations — `audit` (read-only report), `patch` (one finding, one diff, one approval), `revise` (full-art

  • lektorat-auto-revise

    Autonomously works off a `lektorat audit` findings report by routing each artefact by type — documentation to the `audience-doc-author` agent (fully autonomous), blog posts to the `blog-author` skill (assisted) — composing a per-file briefing that binds the audience artefact and writing-style spec,

  • mermaid-diagrams-apply

    Audits and applies the MkDocs Mermaid setup of the current repository against `spec/project/mermaid-diagrams/<canonical_language>.md`, and helps an author add a single Mermaid diagram (hand-described or derived). Wires up `pymdownx.superfences`, pins `pymdown-extensions`, refuses `mkdocs-mermaid2-pl

  • mkdocs-structure-apply

    Audits a repository against the canonical-language file under spec/project/mkdocs-structure/ and, with per-item user approval, scaffolds or patches the MkDocs skeleton: the per-language docs/ tree, seven standard nav sections, plugin baseline (incl. mkdocs-include-markdown-plugin), required `site_ur

  • permission-allowlist-maintain

    Curates the committed `.claude/settings.json` `permissions.allow` list of the current repository per `spec/claude/permission-allowlist/`. Proposes additions sourced from the `fewer-permission-prompts` built-in or from the user, applies the spec's three-condition selection criteria (frequent + read-o

  • portfolio-audit

    Audits, renders, and bootstraps the cross-repository capability portfolio across `nolte/*` per `spec/portfolio/portfolio-management/`. Audit dispatches portfolio-manifest-collector agent for read-only inventory collection, then detects capability duplicates, surfaces gaps, verifies tech-stack consis

  • portfolio-inflight-triage

    Runs the read-only periodic in-flight audit across nolte/* per `spec/portfolio/portfolio-inflight-management/`. Dispatches `portfolio-inflight-collector` for the four data sources (open issues, open PRs incl. drafts, branches without active PR, unresolved review threads + Discussions), applies spec

  • project-structure-apply

    Audits a repository against the canonical-language file under spec/project/project-structure/ and scaffolds or patches missing artefacts: README (delegated mid-flow to `readme-structure-apply`), top-level orientation file, .gitignore, .pre-commit-config.yaml, Renovate config, Taskfile, the MkDocs si

  • pull-request-create

    Creates a GitHub pull request that conforms to the repository's pull-request-workflow spec. Invoke when the user asks to open a PR, create a pull request, draft a PR description, create a merge request, or push the branch and open a PR. Also handles equivalent German-language requests. Don't use to

  • pull-request-merge

    Promotes an open draft pull request on the current branch to a merged state on `develop`, applying repository-declared labels and passing every gate from the pull-request-workflow spec. Invoke when the user asks to promote the draft PR, ship the PR, merge the draft, or bring the PR over the finish l

  • pull-request-runner-sweep

    Finds the current pull request among the open ones targeting `develop` and cancels the in-flight and queued pull-request workflow runs of every other open PR, so the shared runner pool serves only the PR that merges next. Ranks candidates deterministically (explicit operator pick, then ready over dr

  • readme-structure-apply

    Audits the repository's `README.md` against the canonical-language file under spec/project/readme-structure/ and, with per-item user approval, scaffolds or patches the file: H1 + tagline, CI badges, six required sections in order (Purpose, Usage, Structure, Related repositories, Status, License), th

  • release-notes-curate

    Augments the open release-drafter draft on develop with project-context-aware sections per the canonical-language file under spec/project/release-skill-layer/ §\"Skill A — Draft notes curation\". Reads the project's audience artefact, derives a section bundle from the detected project type, wraps th

  • release-publish-trigger

    Validates every release-automation pre-publish gate locally, then dispatches release-publish.yml via `gh workflow run` for the open release-drafter draft on develop, per the canonical-language file under spec/project/release-skill-layer/ §\"Skill B — Release publish trigger\". Verifies that exactly

  • requirements-elicit

    Runs the requirements-elicitation interview methodology from spec/project/requirements-elicitation/ to capture a user's requirements precisely, assuming the user often does not know exactly what they want, expresses it imperfectly, or is misread. Drives a one-question-at-a-time funnel interview, mai

  • spec-drift-audit

    Audits every spec under spec/<topic>/<slug>/ against the repository implementation (source code, config, workflows, docs) and produces a traceable audit artifact per spec/project/spec-drift-audit/. Invoke when the user asks to "run the quarterly spec-drift audit", "check spec versus implementation",

  • spec

    Creates, translates, indexes, deduplicates, and drift-checks multilingual specifications stored under the project's spec/ folder. Invoke when the user wants to write a new spec, update or translate an existing one, check whether a requirement is already covered, regenerate the spec index, or verify

  • tech-stack-capture

    Captures or refreshes the `tech_stack:` block in a Portfolio-Member's `project/portfolio.yml` per the canonical-language file under `spec/portfolio/tech-stack-discovery/` §Discovery sequence. Probes repo signals (lockfiles, `Taskfile.yml`, `.github/workflows/`, `renovate.json5`, `mkdocs.yml`, `.vale

  • vocab-drift-audit

    Audits repository-local Vale vocabularies against the pinned upstream release of nolte/vale-style to detect drift. Dispatches vocab-drift-scanner agent for the read-only diff step; follow-up actions (delete entries, bump pin, draft upstream PR) stay user-controlled in this skill. Invoke when the use

  • workflow-health-triage

    Triages a failing GitHub Actions workflow run on `develop` or `main` per `spec/project/workflow-health/`. Classifies the failure into one of `defect` / `flake` / `infra` / `stale pin` / `secret drift` / `other`, dispatches the most specialised Claude agent that matches the classification, records th

  • working-copy-start

    Orchestrates the start of a new parallel working copy (git worktree) and makes it ready for work, per spec/project/parallel-working-copies/. Invoke when the user asks to "start a new working copy", "set up a worktree for feature X", "spin up a worktree and a plan", "begin work on a new branch in its

  • yaml-json-schema

    Authors, audits, refactors, and validates YAML-encoded JSON Schema 2020-12 documents per `spec/project/yaml-json-schema/`. Scaffolds a new `<slug>-v1.0.schema.yaml` with all mandatory skeleton entries in spec order; audits existing `*.schema.yaml` files for dialect drift, missing identity, inline du

Subagents (18)

  • audience-doc-author

    Drafts or refines an audience-tailored doc (README, release notes, MkDocs pages, or any doc governed by spec/project/) against an existing `audience-identify` artifact. Invoke to write, draft, or refactor a doc for specific audiences; also German. Needs the audience artifact first (dispatch `audienc

  • audience-review

    Read-only review of an existing audience-analysis artifact against `spec/project/audience-identification/` (release notes also against release-notes-audience-analysis); returns a structured findings report, no edits. Invoke to review, audit, validate, or check an audience list's completeness, or whe

  • cicd-pipeline-reviewer

    Read-only audit of a repository's CI/CD pipeline against spec/project/continuous-integration/, spec/project/continuous-delivery/, and spec/project/github-actions-best-practices/: stage sequence and omissions, floating references and unpinned actions, permission scope, untrusted-input handling, cache

  • cookiecutter-template-author

    Scaffolds or refactors a Cookiecutter template (its pre_prompt/pre_gen/post_gen hooks and a pytest-cookies harness) so the rendered project conforms to the bound nolte spec corpus. Invoke to scaffold, author, or refactor a Cookiecutter template, harden a hook, or set up a pytest-cookies harness; als

  • diagram-opportunity-reviewer

    Read-only prose scanner that flags Markdown passages better expressed as a Mermaid diagram. Walks the in-scope set (default docs/<lang>/**/*.md), matches prose against the `spec/project/mermaid-diagrams/` catalog, and returns JSON findings for the dispatching skill to persist; writes nothing. Twin o

  • docs-freshness-checker

    Read-only audit of the current repo's MkDocs docs for freshness: multi-language parity (docs/en vs docs/de), dead internal links, stale references into spec/ or src/, ADR index/status hygiene, Mermaid derived-source drift, and TODO/placeholder markers. Returns a severity-sorted report, never edits.

  • lektorat-scanner

    Read-only editorial scanner dispatched by `lektorat-apply`: walks an in-scope Markdown set and returns a structured findings inventory across six dimensions (D1 readability, D2 comprehensibility, D3 grammar, D4 style, D5 audience-fit, D6 idiomatic naturalness) with severities critical/warning/sugges

  • link-rot-scanner

    Read-only audit of the repo's docs for dead links: internal relative links, intra-page anchors, cross-tree references, and external http(s) URLs probed over the network. Wraps scripts/check_links.py and triages findings into a severity-sorted report, classing network flakiness as warning not rot. In

  • mermaid-diagram-reviewer

    Read-only static audit of every Mermaid block in docs/<lang>/ against spec/project/mermaid-diagrams/ plus the MkDocs setup (mkdocs.yml, docs/requirements.txt). Returns structured findings routed through `mermaid-diagrams-apply` or direct edits; does not render (CI's mkdocs build --strict does). Invo

  • portfolio-inflight-collector

    Read-only in-flight data collector dispatched by `portfolio-inflight-triage`: gathers open issues, open PRs (incl. drafts), branches without an active PR to develop, and unresolved review threads plus open Discussions across the nolte portfolio. Returns raw per-repo data only; severity classificatio

  • portfolio-manifest-collector

    Read-only inventory collector dispatched by `portfolio-audit`: gathers each repo's project/portfolio.yml manifest across all nolte portfolio members and returns the raw tech-stack and capability inventory. Detection only; duplicate/gap analysis and any writes stay with the calling skill. Don't use f

  • project-structure-reviewer

    Read-only audit of the current repo against spec/project/project-structure/, producing a severity-sorted findings list routed through `project-structure-apply` or direct edits. Checks files/directories on disk only; live GitHub-App checks belong to `project-structure-apply`. Invoke to audit project

  • prose-vale-curator

    Curates prose so it passes Vale, preferring shipped-vocabulary terms, and (only inside a repo that owns Vale vocabulary source, e.g. nolte/vale-style) extends an accept.txt for a legitimate technical identifier. Invoke to make a doc Vale-clean, fix Vale alerts, or rephrase until Vale is green; also

  • security-requirements-reviewer

    Read-only security architect's review of a project's requirement/spec set (requirements, ADRs, spec docs) for security and privacy completeness, before or independently of implementation. Judges whether each requirement specifies the controls it needs, detecting requirement sources at runtime; retur

  • spec-readiness-reviewer

    Read-only audit of specs under a target topic for downstream readiness along three dimensions: contradictions (intra- and cross-spec), audience fit, and domain completeness (Requirements-to-Acceptance-Criteria coverage, load-bearing Open Questions, ghost references). Returns a severity-sorted report

  • tech-stack-drift-reviewer

    Read-only audit of a repo's declared tech-stack manifest (project/portfolio.yml tech_stack: for members; portfolio/tech-stack.yml globally) against spec/portfolio/tech-stack/ and tech-stack-discovery/, plus on-disk signals (lockfiles, configs, workflows), to detect declared-vs-actual drift. Returns

  • tech-stack-fitness-reviewer

    Read-only architect's review evaluating a project's declared tech stack for fitness against its own functional and non-functional requirements: coverage, gaps, over-/under-engineering, risks, and stack-vs-requirement contradictions. Detects requirement sources and the stack at runtime; returns a sev

  • vocab-drift-scanner

    Read-only scanner dispatched by `vocab-drift-audit`: diffs repository-local Vale vocabulary files against the pinned upstream nolte/vale-style release and returns a two-section drift report (local entries already accepted upstream to delete; local entries not yet upstream as PR candidates). Follow-u

View source on GitHub nolte.github.io

More from nolte/claude-shared

All 5 plugins →

Engineering capabilities for code-bearing projects: full-stack implementation, the test-tier and test-cycle suite, the quality gate, frontend/web-UI optimization, and code-security / dependency / license auditing. Code repositories adopt this on top of nolte-shared.

19 skills · 39 agents

0

Project-planning cadence for repositories that plan in project/: SMART mission authoring, roadmap init/planning/refinement, roadmap-item decomposition into features, and the sprint lifecycle from planning through execution to review, with the matching readiness, coherence, and consistency reviewers. Adopt this on top of nolte-shared only if your repository runs a mission/roadmap/feature/sprint cadence; repositories that track work as issues never do.

9 skills · 3 agents

0

Claude Code skill and agent authoring for plugin/skill developers: spec-conformant skill/agent scaffolding and revision, skill and agent review, portfolio-wide skills/agents sweeps, and skills/agents documentation-catalog generation. Adopt this on top of nolte-shared only if you author Claude Code skills or agents; the majority of consumers never do.

5 skills · 1 agent

0

Brand-aware image generation and media processing: provider-pluggable text-to-image, manual Gemini handoff, brand-conformant prompt authoring, and PNG-to-transparent-SVG vectorisation. Requires external image-generation credentials and binaries.

2 skills · 2 agents

0

Maintain nolte-shared?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins5 plugins