"All my stateless tools (like Jira, AWS, GitHub) have been migrated to simple CLIs." - How do you get Jira on the CLI?
How I use every Claude Code feature
61–70 of 193 posts
Re: How I use every Claude Code feature
#62> Finally, we keep this file synced with an AGENTS.md file to maintain compatibility with other AI IDEs that our engineers might be using. I researched this the other day, the recommended (by Anthropic) way to do this is to have a CLAUDE.md with a single line in it: @AGENTS.md Then keep your actual content in the other file: https://docs.claude.com/en/docs/claude-code/claude-code-on-t...
Re: How I use every Claude Code feature
#63I have started experimenting with a skills/ directory in my open source software, and then made a plugin marketplace that just pulls them in. It works well, but I don't know how scalable it will be.
Re: How I use every Claude Code feature
#64"All my stateless tools (like Jira, AWS, GitHub) have been migrated to simple CLIs." - How do you get Jira on the CLI?
Re: How I use every Claude Code feature
#65Earlier quoted context omitted.
They all have optional ide integration, e.g Claude knows the active vscode tab and highlighted lines.
Is that better than Cursor? Same? Just different?
There's even an official Anthropic VS Code extension to run CC in VS Code. The biggest advantage is being able to use VS Code's diff views, which I like more than in the terminal. But the VS Code CC extension doesn't support all the latest features of the terminal CC, so I'm usually still in the terminal.
Re: How I use every Claude Code feature
#66"All my stateless tools (like Jira, AWS, GitHub) have been migrated to simple CLIs." - How do you get Jira on the CLI?
Latest version from 2 momths ago, >4700 stars on GitHub
Re: How I use every Claude Code feature
#67Crazy how fast Claude Code is evolving, every week there’s something new to learn, and it just keeps getting better.
Re: How I use every Claude Code feature
#68Re: How I use every Claude Code feature
#69> Finally, we keep this file synced with an AGENTS.md file to maintain compatibility with other AI IDEs that our engineers might be using. I researched this the other day, the recommended (by Anthropic) way to do this is to have a CLAUDE.md with a single line in it: @AGENTS.md Then keep your actual content in the other file: https://docs.claude.com/en/docs/claude-code/claude-code-on-t...
You think it would be a good idea to use a symlink instead?
The recommended approach has the advantage of separating information specific to Claude Code, but I think that in the long run, Anthropic will have to adopt the AGENTS.md format
Also, when using separate files, memories will be written to CLAUDE.md, and periodic triaging will be required: deciding what to leave there and what to move to AGENTS.md
Re: How I use every Claude Code feature
#70Crazy how fast Claude Code is evolving, every week there’s something new to learn, and it just keeps getting better.
Nothing crazy about it, judging by how much CPU and memory it uses. Now, if it managed to grow features without bringing my M4 Mac with 64GB of ram to a crawl... that's be magic .