(feat): Enhancements to Spec Kit #986
Conversation
localden
added
enhancement
templates
…into localden/vscode
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 19 out of 19 changed files in this pull request and generated 2 comments.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 21 out of 21 changed files in this pull request and generated 3 comments.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
in vscode insiders i have a warning saying "Chat modes have been renamed to agents. Please move this file to .github/agents/speckit.[prompt].agent.md". should you not put this inside the new designated folder and file from vscode ? |
|
I recommend that chatmodes, prompts should be named with prompt name first and .speckit after. So instead of speckit.plan it will be better to save as |
|
Hey guys, just two linting errors to fix pls. Seems the spec-it popularity is driving crazy release api rate limits and it's almost impossible to use |
|
I was just going to say the same thing @Nosafe did 😆 They've officially moved from |
| # Create prompt file with agent frontmatter | ||
| cat > "$prompt_file" <<EOF | ||
| --- | ||
| agent: ${basename} |
There was a problem hiding this comment.
I didn't see any tools loaded anywhere—has this given you issues before? Every single time I forget to set a tool back in one of these agent files, it seems to stop everything... but as frequently as they're changing things, I've stopped trying to guess. 😆 Just calling out as something to verify before you merge.
|
|
||
| 1. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote. | ||
|
|
||
| **UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL** |
There was a problem hiding this comment.
Just a thought: Do you think it would be worth it to hard-code these checks in and not even load the prompt if the repo doesn't match? It's really more of a longer-term solution but might be worth a discussion. I'm not sure what that would even look like, tbh, but maybe worth a discussion at some point 🤷🏻♀️
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 21 out of 21 changed files in this pull request and generated 3 comments.
Comments suppressed due to low confidence (1)
src/specify_cli/init.py:1288
- 'except' clause does nothing but pass and there is no explanatory comment.
except Exception:
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 21 out of 21 changed files in this pull request and generated 5 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…into localden/vscode
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 21 out of 21 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Refactored both Bash and PowerShell create-new-feature scripts to modularize and deduplicate logic for determining the next feature number, including new helper functions for extracting the highest number from specs and branches. Improved branch name cleaning and generation. In update-agent-context scripts, removed redundant updates to AGENTS.md for Copilot, streamlining agent update logic.
…into localden/vscode
Description
versioncommand. (specify --version flag not supported, returns error #486)Screenshots
Hand-offs
Version
References
Behavior notes