Generate an 11-section Step 1 specification from a PR diff and metadata.
npx skills add https://github.com/MinhOmega/marlin-skill --skill task-submit
Please help me install this Agent Skill. Skill: task-submit Source: https://github.com/MinhOmega/marlin-skill/tree/main/.claude/skills/task-submit Command: npx skills add https://github.com/MinhOmega/marlin-skill --skill task-submit
The task-submit skill automates turning a PR diff and associated metadata into a complete Step 1 specification for the Snorkel submission form, ensuring consistency and completeness without manual drafting.
Provide a PR diff and corresponding metadata in the workspace to generate a complete Step 1 specification document ready for review.
High-intent search queries and answers about installing and using this skill.
To generate specification documentation from a PR diff, you need a workspace containing the pr.diff file and meta.json. The task-submit skill processes these inputs to automatically produce a complete, fixed 11-section specification document ready for review without manual drafting.
Automating the Snorkel submission form from a pull request requires providing the PR diff and associated metadata. The system transforms these inputs into all 11 required Step 1 specification fields, ensuring consistency and completeness for the final submission.
Turning a PR diff into a spec doc requires generating 11 fixed sections: Project Version, Prompt Category, Repo Definition, PR Definition, Edge Cases, Acceptance Criteria, Testing Setup, Setup Notes, Initial Prompt, and Automated Feedback Disagreements to populate the submission form.
Yes, the specification generation process validates outputs before finalizing by enforcing an anti-llm validator. It applies internal validation gates and rewrite checks to the PR diff and metadata to minimize rejected outputs and ensure production-ready pre-submission specs.
To generate PR review specifications, your workspace must contain a pr.diff file and a meta.json file. These files provide the necessary code changes and project context to automatically populate all required fields of the Step 1 specification.
Yes, you can use this to standardize how PRs are transformed into production-ready specs. It fits directly into PR workflows to consistently convert diffs and project metadata into a complete Step 1 specification, eliminating manual drafting inconsistencies.
aRustyDevCreate a new Claude Code Skill directory with SKILL.md, justfile, and meta.json.
MazenMradGuide an 11-step workflow to produce a complete Narrative Design Document.
sommioOrchestrate multi-agent code reviews and merge findings into a single report.
DigiBanks99Guide collaborative drafting of documents through a three-stage workflow in Markdown tooling.
