haskell-agent

Enforce Haskell release protocols and development standards across ~/haskell/ packages.

101|3|Updated Sep 2, 2021
One-click install
npx skills add https://github.com/tonyday567/haskell-agent --skill haskell-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: haskell-agent
Source: https://github.com/tonyday567/haskell-agent/tree/main
Command: npx skills add https://github.com/tonyday567/haskell-agent --skill haskell-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Haskell-agent Skill provides a canonical guide for release protocol, development standards, and deep patterns for the ~/haskell/ ecosystem, helping teams apply consistent practices across projects.

Core Features & Use Cases

  • Comprehensive eight-phase Release Protocol covering environment, dependencies, code quality, docs, and publishing.
  • Clear conventions for imports, exports, module structure, and doctests across Haskell projects.
  • Dev toolkit and default files to accelerate setup for new or existing packages under ~/haskell/.

Quick Start

Load this skill when starting any Haskell package under ~/haskell/ and follow the eight-phase release protocol

Frequently Asked Questions about haskell-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the Haskell release protocol and when do I need it?

The Haskell release protocol is an eight-phase process covering environment, dependencies, code quality, docs, and publishing. You need it when preparing releases, setting up new packages, or enforcing conventions across projects in the ~/haskell/ workspace.

How do I set up a new Haskell package with standard conventions?

To set up a new Haskell package, load this skill to apply canonical conventions for imports, exports, module structure, and doctests. It provides a dev toolkit and default files to accelerate setup for packages under ~/haskell/.

What are the best conventions for Haskell imports, exports, and doctests?

The best conventions for Haskell imports, exports, and doctests involve applying a canonical guide that defines clear module structure and doctest standards. This enforces consistent development practices across eligible packages in the ~/haskell/ ecosystem.

Does this Haskell release protocol work for existing packages or only new projects?

This Haskell release protocol works for both existing packages and new projects. It provides default files and a dev toolkit to accelerate setup for new or existing packages under ~/haskell/, ensuring consistent practices across the ecosystem.

How do I run doctests as part of a Haskell CI build process?

To run doctests in a Haskell CI build process, follow the eight-phase release protocol which includes code quality checks. The protocol enforces clear conventions for doctests across Haskell projects to ensure consistent validation during builds.

Why should I use a standardized protocol for Haskell build and release preparation?

You should use a standardized protocol for Haskell build and release preparation to enforce consistent development standards and deep patterns across teams. It provides a canonical guide covering dependencies, code quality, docs, and publishing to reduce errors and maintain ecosystem consistency.