jds-finish

Verify completed JDS sessions and clean up temporary working artifacts.

13|Updated Mar 24, 2026

Search Tags:#workflow #documentation #verification #cleanup #artifacts #finish #jds

Ready to run

npx skills add https://github.com/josipmusa/jds --skill jds-finish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jds-finish
Source: https://github.com/josipmusa/jds/tree/main/skills/jds-finish
Command: npx skills add https://github.com/josipmusa/jds --skill jds-finish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finalizes a JDS session by performing the last verification and cleanup of working artifacts, ensuring no residual state or uncommitted changes remain.

Core Features & Use Cases

Final verification: confirms that jds-verify completed successfully before cleanup.
Artifact cleanup: deletes temporary session data and artifacts created during the workflow.
Safety boundary: does not commit, push, or create PRs; those actions are the caller's responsibility.

Quick Start

Run the final verification and clean up all JDS working artifacts from the current session.

Frequently Asked Questions about jds-finish

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

FAQPage Schema

How do I clean up temporary session artifacts after completing a workflow?▼

To clean up temporary session artifacts after completing a workflow, you run a final verification and cleanup process. This confirms prior verification succeeded and deletes residual session data, ensuring no unintended working state remains.

What is the best way to verify workflow completion before deleting artifacts?▼

The best way to verify workflow completion before deleting artifacts is to run a final verification step that checks prior verification succeeded. This prevents cleanup from occurring on incomplete sessions and removes residual temporary data safely.

Does artifact cleanup automatically commit changes or create pull requests?▼

Artifact cleanup does not automatically commit changes, push, or create pull requests. It acts as a safety boundary by only deleting temporary session data, leaving all version control actions to the developer or caller.

When do I need to run final artifact cleanup in a software engineering workflow?▼

You need to run final artifact cleanup in a software engineering workflow when all plan tasks are completed and initial verification has executed. This timing ensures no residual artifacts remain and prevents unintended commits during session teardown.

Why does residual session data remain after workflow tasks are finished?▼

Residual session data remains after workflow tasks are finished because temporary artifacts are generated during execution and require a dedicated cleanup step to delete. This final step verifies prior checks succeeded and removes all residual artifacts.