Thanks to visit codestin.com
Credit goes to github.com

Skip to content

benizzio/spec-kit-coding-standards-drift-control

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Coding Standards Drift Control

Beta Spec Kit extension for reviewing implemented features against the repository coding-standards baseline and appending remediation tasks for drift findings. Track and fix code that moves away from technical definitions while adding the smallest amount of complexity possible to the Spec Kit artifacts.

Features

  • Provides the /speckit.coding-standards-drift-control.report command
  • Provides the /speckit.coding-standards-drift-control.remediation-plan command
  • Registers an optional after_implement hook for report generation
  • Uses AGENTS.md, .specify/memory/constitution.md, and other known agent-instruction files as the review baseline when present
  • Focuses on coding standards and engineering practices rather than feature-domain correctness
  • Blocks report generation and remediation planning while the active feature has open or pending tasks
  • Uses CODE-STAND-DRIFT-### finding identifiers, preserves historical findings with Pending/Resolved status, and migrates legacy DRIFT-### findings to the new format on rerun
  • Records concise per-finding remediation plans in the drift report before appending tasks to tasks.md so /speckit.implement can execute them

Requirements

  • Spec Kit >=0.2.0
  • A Spec Kit project with .specify/
  • An active feature with spec.md, plan.md, and tasks.md

Installation

Release Install

specify extension add coding-standards-drift-control --from https://github.com/benizzio/spec-kit-coding-standards-drift-control/archive/refs/tags/v0.4.0.zip

Development Install

specify extension add --dev /path/to/spec-kit-coding-standards-drift-control

Workflow

  1. Finish the active feature's normal implementation tasks.
  2. Run /speckit.coding-standards-drift-control.report to generate or incrementally refresh coding-standards-drift-report.md.
  3. Run /speckit.coding-standards-drift-control.remediation-plan to record remediation plans in the report and append a drift remediation phase to tasks.md.
  4. Execute the generated remediation tasks with /speckit.implement.

Commands

/speckit.coding-standards-drift-control.report

Generates or incrementally refreshes specs/{feature}/coding-standards-drift-report.md for the active feature after implementation is complete.

Example:

/speckit.coding-standards-drift-control.report focus on parser and validation files

/speckit.coding-standards-drift-control.remediation-plan

Adds or updates per-finding remediation plans in specs/{feature}/coding-standards-drift-report.md, then appends a final remediation phase to specs/{feature}/tasks.md from those plans.

Example:

/speckit.coding-standards-drift-control.remediation-plan only high severity drift items

Behavior

  • Reviews the active feature implementation against repository policy files and local engineering standards
  • Loads AGENTS.md, .specify/memory/constitution.md, and known agent-instruction files such as CLAUDE.md, GEMINI.md, .github/copilot-instructions.md, .cursorrules, .cursor/rules/**, .windsurfrules, and .clinerules when present
  • Falls back to a conservative baseline derived from the local codebase when those files do not define concrete standards
  • Keeps findings grounded in exact file references and explicit policy evidence
  • On rerun, keeps prior report findings, appends newly discovered drift as Pending, and leaves Resolved transitions to the final generated remediation task
  • The remediation-plan command reasons from the report evidence and coding-standards baseline references before recording a surgical Remediation plan for each selected pending finding
  • Skips remediation task generation when the report has no pending findings or when a matching CODE-STAND-DRIFT-### task, or a legacy DRIFT-### task for the same finding, already exists in tasks.md

Configuration

No additional extension configuration file is required. The commands inspect the active Spec Kit feature artifacts and repository policy files at runtime.

Output

  • specs/{feature}/coding-standards-drift-report.md with optional per-finding remediation plans
  • specs/{feature}/tasks.md with an appended drift remediation phase

Troubleshooting

Report Generation Stops Immediately

Complete the remaining open or pending tasks in the active feature's tasks.md, then rerun the report command.

No Remediation Tasks Were Added

Either the report contains no pending findings, or matching CODE-STAND-DRIFT-### tasks (or legacy DRIFT-### tasks for the same pending findings) already exist in tasks.md.

specify extension Commands Are Missing

Install the Spec Kit CLI from the GitHub repository rather than the unrelated PyPI stub package:

uv tool install specify-cli --force --from git+https://github.com/github/spec-kit.git

Release Notes

  • Repository: https://github.com/benizzio/spec-kit-coding-standards-drift-control
  • Documentation: README.md
  • Changelog: CHANGELOG.md
  • License: MIT
  • Current beta version: 0.4.0

Catalog Submission Metadata

  • Extension ID: coding-standards-drift-control
  • Extension Name: Coding Standards Drift Control
  • Version: 0.4.0
  • Commands: 2
  • Hooks: 1
  • Suggested tags: analysis, standards, quality, maintenance

License

MIT

About

A Spec Kit extension for focused analysis and remediation of coding standards drift

Resources

License

Stars

1 star

Watchers

0 watching

Forks

Packages

 
 
 

Contributors