OpenWPM
Official@openwpm
OpenWPM's crosslink skill suite orchestrates issue-tracked feature development: design docs, git worktrees, background agents, QA gates, and audited commits.
Agent Skills by OpenWPM
Showing 13 vetted skills indexed across 1 GitHub repositories.
openwpmcommit
Creates jj commits with conventional messages and records results on crosslink issues.
openwpmdesign
Authors codebase-grounded feature design documents through a four-phase interactive workflow.
openwpmkickoff
Launches a background Claude agent in tmux or containers to implement a feature end-to-end.
openwpmfeatree
Creates a feature bookmark and isolated git worktree with crosslink agent initialization.
openwpmqa
Reviews code and architectures against SOLID, security, and complexity thresholds using the ADIHQ framework.
openwpmmaintain
Runs a periodic codebase health pass covering dependencies, lint, tests, dead code, docs, and issue hygiene.
openwpmaudit
Dumps full crosslink project context including session state, issues, locks, and git status for re-orientation.
openwpmworkflow
Guides a policy review of crosslink configuration covering tracking modes, security rules, and hooks.
openwpmfeature
Creates a feat/<slug> jj branch and registers a matching crosslink issue.
openwpmreview-pre-commit
Reviews working diffs for stubs and debug leftovers, then runs lint, format, and test checks.
openwpmcheck
Inspect status and output of background feature agents running in tmux sessions or containers.
openwpmcrosslink-guide
Documents the crosslink CLI for issue tracking, sessions, locks, swarms, and knowledge pages.
openwpmpreflight
Loads crosslink project rules, language rules, and tracking context before implementation sessions.
Frequently Asked Questions About OpenWPM
FAQPage SchemaWhat tasks can I accomplish with OpenWPM's crosslink skills?▼
You can author design documents, create feature branches and git worktrees, launch background implementation agents in tmux or containers, run architectural QA reviews with complexity thresholds, execute pre-commit quality gates, perform dependency and dead-code maintenance passes, and close the loop with issue-referenced conventional commits.
Who are these skills designed for?▼
They target software engineers working in crosslink-tracked repositories who delegate feature work to background agents. Maintainers needing rigorous architectural review (SOLID, OWASP/NIST, cyclomatic complexity > 15 fails) and developers wanting enforced issue-linked audit trails on every commit benefit most.
How does a typical development session run?▼
Start with preflight to load project and language rules, optionally draft a design doc, then create a feature branch or worktree. Kick off a background agent, monitor it with check, run review-pre-commit for lint/test/stub scanning, and finish with commit, which writes a conventional message and documents the result on the active crosslink issue.
What prerequisites and dependencies are required?▼
A repository initialized with a .crosslink/ directory is required, since skills read its rules, issues, sessions, locks, and hooks. Background agent execution needs tmux or docker/podman. Version control operations rely on jj (Jujutsu) for commits and git for worktrees and feature branches.
How do the skills enforce code quality and security?▼
The qa skill applies the ADIHQ framework with SOLID, DRY/KISS/YAGNI, decoupling, and OWASP/NIST checks, failing code above cyclomatic complexity 15 and emitting a Severity/Dimension/Location/Violation/Refactor matrix. The review-pre-commit skill additionally blocks stubs, debug leftovers, and undocumented issues before any commit lands.